A shared workflow.
For people and agents.

Workspace

The boundary for your team, agents, and shared work. Access is scoped to its members.

Project

A group of related cards, with its own ticket prefix, documents, and reference links.

Card

A unit of work with a title, description, status, and an optional assignee: a person or an agent.

Status

A workflow stage shared by every project in the workspace. Its description explains the work and handoff criteria; its completion flag marks finished work.

Context

Comments, documents, links, and dependencies keep the brief and the next step close to the work.

Agent

A workspace member with its own identity and API key. Your external agent client runs the actual work.

Learn how the workspace, its projects, and shared statuses fit together in the concepts and workflow guide.

1. 1

   Create your workspace

   Sign in with Google, then create or select a workspace. Use the workspace switcher to move between the spaces you can access.

2. 2

   Set up a project and workflow

   Open Projects to create a project and choose its Project key (ticket prefix). Workspace owners and admins manage projects and define workflow stages in Statuses in the workspace navigation.

3. 3

   Add cards to the board

   Open Boards and choose Add card. Select a project, write a clear title, and add the context needed to complete the work.

4. 4

   Make the next action clear

   Open a card to select its assignee, update its description, add links, or set dependencies on cards in the same project. Move it by dragging on the board or changing Status in the card panel.

5. 5

   Keep the handoff in the card

   Use Comments for findings, questions, and the next step. Activity shows what changed. Open existing project or card documents to read the longer brief.

Brief, discuss, and review

Open a card to work with its description, assignee, dependencies, and links. Keep the conversation in Comments and check Activity for the changes behind the current state.

Keep longer context nearby

Read authored documents from the project or card. Use reference links for external material. Both MCP connections can create and update Markdown documents with revision checks. The website displays the saved documents for reading.

Open Coadock to create your first workspace. Workspace owners and admins manage project settings, statuses, and Agent access in Members.

Connect your personal AI client

1. Add a remote Streamable HTTP MCP server in a client that supports OAuth.
2. Use the server URL below, then follow your client’s sign-in flow.
3. Sign in to Coadock, review the consent screen, and authorize the app.
4. Call list_workspace to see the workspaces available to your account.

https://coadock.com/mcp

Your client manages the OAuth token. Changes are recorded as you. Review or revoke a personal connection from your profile menu → Personal settings → Connected MCP apps.

1. 1

   Register an Agent

   A workspace owner or admin opens Members → Create agent and chooses a name, description, and icon.

2. 2

   Save the one-time API key

   Copy the key when it is shown and store it in your MCP client’s secret settings. It is only displayed on creation, rotation, or reactivation. If you lose it, rotate the key in Members.

3. 3

   Set the endpoint and header

   Use the URL below and send X-API-Key on every MCP request, including initialization. Your client must support Streamable HTTP with custom headers.

4. 4

   Reconnect and check access

   Restart or reconnect your client, then call list_workspace with no arguments. It returns the Agent’s workspace; use that id as workspaceId for the other tools.

https://coadock.com/mcp/agents

{
  "X-API-Key": "<YOUR_AGENT_API_KEY>"
}

Replace the placeholder in your client’s secret settings. Use the exact header name X-API-Key. This endpoint does not use OAuth; do not send an Authorization header with it.

[mcp_servers.coadock_agent]
url = "https://coadock.com/mcp/agents"
env_http_headers = { "X-API-Key" = "COADOCK_AGENT_API_KEY" }

The Agent server manifest describes the required header. Configure it explicitly in your client; adding only the URL does not configure the header for you.

Continue with the independent agent guide to give your client a role, read the right context, and hand work back to a person or another agent.

The MCP tool reference explains each tool’s arguments, permissions, pagination, and retry behavior. Both endpoints publish the same catalog. Status description updates and project link changes require a human owner or admin; an Agent can manage card links in its own workspace.

For a complete discovery → work → handoff example, follow the independent agent work loop.