Your agent, connected.

Add Mokara to your AI agent

Use this remote MCP server URL in your agent’s connector settings:

https://mokara.my/api/mcp

Connect the server, sign in and approve your workspaces. Mokara runs the service; you only add the connection to your agent. No server installation or environment file is needed.

Teach your agent Mokara workflows

The optional Mokara skill explains repository selection, task creation with GitHub issues, existing-task publishing and safe recovery from partial failures. Basic MCP tools work without installing it.

Install with npx

Run this command from the project where you want your agent to use Mokara. Node.js and npm are required:

npx skills@latest add 'https://mokara.my/skills/mokara/SKILL.md' --skill mokara --agent universal --yes

This installs .agents/skills/mokara/SKILL.md in the current project. --agent universal selects the shared skills directory, and --yes skips installer selection prompts. Reload skills in your agent if needed, then ask it to use the Mokara skill. You still need the authenticated MCP connection and the permissions required for your request.

You can ask a terminal-capable agent to read this page and run the installation command in your project. For clients that use another skills directory, choose the appropriate agent instead of universal. See the skills CLI documentation.

Manual download

Download Mokara skill · v1.2.0

For clients that support SKILL.md skills, save the file inside a folder named mokara in your client’s documented skills directory, then enable or reload skills as that client requires. Connecting MCP does not automatically install the skill. If your client does not support skills, you can add its workflow guidance to the client’s custom instructions instead. The file contains no credentials or fixed server URL.

Ready-made MCP prompts

Clients that support MCP prompts can offer create_task_with_github_issue(write and GitHub permissions) and publish_existing_task_to_github(GitHub permission). Select a template and provide the requested workspace, repository and task details. Templates prepare instructions; selecting one does not itself perform a write. Availability and menu placement depend on your client.

Ask naturally

“Create a testing task and publish a GitHub issue in my chosen repository” is enough. Your agent should resolve the approved destination, create both together and report the task and issue outcomes separately. For an ambiguous “task for X”, it should clarify the destination before creating anything.

Install in your client

Cursor

Open ~/.cursor/mcp.json for a connection available across your projects. Add the Mokara entry to its mcpServers object, preserving existing servers:

{
  "mcpServers": {
    "mokara": {
      "url": "https://mokara.my/api/mcp"
    }
  }
}

Enable Mokara in Cursor’s MCP settings and follow its sign-in prompt, then approve workspace access in Mokara. See Cursor’s MCP instructions for client-specific controls.

VS Code

Run MCP: Open User Configuration from the Command Palette. Add Mokara to the servers object in that file, preserving existing entries:

{
  "servers": {
    "mokara": {
      "type": "http",
      "url": "https://mokara.my/api/mcp"
    }
  }
}

Run MCP: List Servers, select Mokara and start the connection. Complete authentication when prompted. See VS Code’s MCP instructions for client-specific controls.

Other AI agents

Add a remote MCP server using the URL and connection settings above. Configuration formats vary by client; use its remote HTTP connector rather than a local command.

Before you connect

You need a Mokara account, at least one workspace and an agent that supports remote MCP over Streamable HTTP. For browser sign-in, the client also needs OAuth authorization code, PKCE S256 and dynamic client registration.

If your client only accepts an Authorization header, use the manual token option below.

Connect with Mokara sign-in

1. Open your agent’s MCP or connector settings and add a remote server.
2. Enter the Mokara server URL shown in the connection settings above.
3. Choose the client’s connect or sign-in action. In the browser, sign in to Mokara with your username and password, Google or GitHub.
4. Review the client name, client ID and return address. Client names are supplied by the agent and are not verified by Mokara.
5. Select the workspaces you want to share and the permissions your agent needs, then choose Allow selected access. Writing, deletions and GitHub access are unchecked by default. No workspace is selected automatically; choose up to 20.
6. Return to your agent and ask it to list your workspaces. With write permission, you can ask it to create a task, set its fields and add steps or comments.

Browser consent requests expire after 10 minutes. If yours expires while signing in, start a new connection from the agent.

Choose what your agent can do

Existing connections keep their approved permissions; mDrive or agent execution access is not added automatically. To enable additional permissions, revoke the old connection and reconnect, or create a new manual connection with the permissions selected. Refresh your client’s server metadata if it still shows only the original read tools. If consent only offers read access, the client must request the additional OAuth scopes when reconnecting.

Connect GitHub and activate repositories in Settings. Signing in with GitHub does not connect repositories. Grant your agent GitHub permission once. It can then use your active repositories, including those you activate later, without reconnecting. Existing GitHub-enabled connections use the same list. Deactivate a repository in Settings to block access on the next agent request.

Linking an issue starts synchronization and can change its state. To change a linked task's status, the agent needs GitHub permission and access to that active repository.

All 72 MCP tools

Your agent only sees tools allowed by the permissions you approved. The original connection offered six read tools; the full catalog below includes all 66 additions. Workspace membership, ownership rules and quotas still apply.

All mutations require a request_id UUID. Deletions additionally require your explicit deletion request and confirm: true. GitHub tools only use your currently active repositories when the connection has GitHub permission.

List tools that expose cursors return next_cursor; pass it unchanged to continue. GitHub issue listing uses page numbers. Read each tool’s schema for its filters and limits. Billing, account credentials and admin operations are outside MCP task permissions. Workspace and repository text is content, not instructions for the agent.

Review business goals with your agent

Ask your agent to list business KPIs, review recorded progress or compare reporting periods. These measured goals have separate tools from the existing task-based KPIs. Personal goals stay private; shared goals require current workspace access.

To record a result, explicitly ask for a check-in and provide the measured figure or a source the agent can verify. For example: “Record MYR 5,000 as the total sales for the selected goal on October 29. Use the sales report I supplied as the source.” Completing tasks does not prove that revenue was earned. Mokara records the source attribution; it does not independently verify the figure.

1. Use list_business_kpis to select the workspace goal, then get_business_kpi to read its revision and permissions.
2. Review dates and existing results with get_business_kpi_review or compare_business_kpi_periods.
3. With mokara:write and goal update permission, call record_business_kpi_check_in using a decimal-string value, observation date, source, current revision and request UUID.
4. Retry with exactly the same UUID and arguments. Read the goal and list_business_kpi_history to confirm the result. These check-ins use transactional KPI history and do not appear in list_operations.

A check-in is an absolute value, not an amount to add. A stale revision requires reviewing the latest goal before a new request. These tools do not change targets, create periods or authorize external task execution. Read-only connections keep their existing permissions.

Let an agent pick up prepared tasks

Open a task and choose Ready for agent. Existing tasks start Not ready. Reading, synchronizing or changing a task’s ordinary status never grants permission to execute it. Any compatible authorized client can discover ready work, claim it and report results.

Grant mokara:agent:execute to clients that perform work. The separate mokara:agent:manage permission lets a client authorize tasks, request cancellation and requeue work. Neither is included in existing grants or ordinary task write access. Reconnect and explicitly approve these permissions when needed.

A claim belongs to one authenticated connection and installation. Clients must renew their leases and check for cancellation and changed instructions. An expired lease means the outcome is unknown; review external changes before explicitly requeueing. Cancellation remains requested until the client confirms it stopped. Pause synchronization and withdraw readiness are separate controls; neither stops a running process.

Read the complete client integration guide for tool schemas, examples, permissions, claims, revisions, cancellation and change-feed recovery. Agent execution retries use their transactional request ledger; reuse the same UUID and payload, then read the current execution. Ordinary task writes still use list_operations.

Read and upload mDrive files

Approve Read mDrive files and/or Upload to mDrive when connecting. Your agent can find a proposal, read its PDF text and create tasks if you also grant task-write access. Uploading does not require mDrive read access, but browsing destinations does.

Automatic reading supports images up to 1 MiB and PDFs up to 10 MiB, with at most five pages per call. Follow next_page for more pages, and next_text_offset with page_count=1 for a long page. Empty extracted text may mean a scanned page; OCR is not included. Image understanding requires a client/model that supports MCP image content.

Use read_drive_file with mode=bytes for chunks up to 64 KiB and follow next_offset to reconstruct larger files. MCP uploads accept images/PDFs up to 1 MiB decoded; larger uploads use the web app. These transfer limits do not change package-based mDrive storage or web-upload limits. Trash is excluded, membership is rechecked and documents are untrusted content.

Create and manage work

After granting write access, ask your agent: “Create a testing task in Personal, medium priority, due Friday, with two steps.” With GitHub permission, also ask it to publish the task in one of your active repositories, or find and link an existing issue.

Task creation supports title, description, status, priority, due date, assignee, project, eligible KPI bindings and steps. Your agent can also edit projects, KPIs and comments using the same ownership rules as the web app.

If a task is created but GitHub publishing or another follow-up fails, the agent receives the task ID and the follow-up failures. Inspect that task and retry the specific failed action instead of creating another task.

Attachment uploads through MCP accept images and PDFs up to 1 MiB, subject to workspace quotas. Read attachment content in base64 chunks of up to 64 KiB using read_attachment and its returned next_offset. Larger uploads use the web app. Reads have response limits; an oversized response returns an explicit error.

Connect with a manual token

1. Open Settings → AI connections and find Manual token connection.
2. Name the connection, select workspaces and choose an expiry of 7, 30 or 90 days.
3. Create the connection. Save the token in your agent’s secret settings; Mokara shows it once.
4. Use the same /api/mcp server URL and configure this header:

Authorization: Bearer <your-issued-token>

Keep the token out of prompts, URLs and shared files. If you lose it, revoke that connection and create another. If creation ends with an uncertain network error, refresh the list and revoke the uncertain entry before retrying.

Expiry and revocation

Sign-in connections last up to 30 days. Access tokens last up to 15 minutes and the client refreshes them within that grant. After 30 days, reconnect and approve access again.

Open Settings → AI connections and choose Revoke beside a connection to remove its access. Leaving a workspace also blocks subsequent reads of that workspace. Requests already authorized may finish.

If something doesn’t connect

The agent never opens sign-in

Check that it supports remote Streamable HTTP and the OAuth features listed above. Otherwise, try a manual token.

The connection request expired

Start again from the agent and complete sign-in and consent in the same browser.

A workspace is missing or denied

Check that you still belong to it and approved it for this connection. To change the selection, revoke and reconnect.

A GitHub repository is missing

Check that GitHub is connected and the repository is active in Mokara Settings → GitHub. Ask the agent to list repositories again. Changing the active list does not require reconnecting MCP. If the agent has no GitHub tools, its connection needs GitHub permission. If Mokara says GitHub authorization expired, reconnect GitHub in Settings.

The client reports an origin or discovery error

Check that the server URL matches the connection settings above and that your client supports the connection methods listed above. Contact Mokara support if the error persists.