Connect an MCP client

TalentOS runs an MCP server. Connect a client to it and your coding agent can read what your workspace has published, without you pasting anything in by hand. Setup takes about two minutes.

You need an API key first. See Create an API key for an external tool.

Connect the client

1. Open Settings in the console, choose the API & MCP tab, and find the Other MCP clients card.
2. Open the MCP config tab and copy the JSON block for a .mcp.json file or a desktop client's config:

{
  "mcpServers": {
    "talentos": {
      "command": "npx",
      "args": ["-y", "talentos"],
      "env": {
        "TALENTOS_API_KEY": "tos_your_key_here"
      }
    }
  }
}

3. Replace tos_your_key_here with your real key.
4. Save the client configuration and restart the client.
5. Ask it to list your TalentOS workflows.

The published talentos package already knows which address to call, so the key is the only workspace credential you supply.

A worked example

Your ops lead keeps a published Skill called "Weekly pipeline report". After connecting an MCP client, ask:

Using the talentos tools, list what our workspace has published, then show me "Weekly pipeline report" as a markdown runbook.

The client calls list_workflows, then get_workflow, and prints the runbook. You can now work against it locally without copying anything out of the console by hand.

What the connection can and cannot do

The server exposes six tools: get_context, list_workflows, get_workflow, list_nodes, create_skill, and update_skill. The names still say "workflow" in places where the console now says Skill or Routine.

• It acts as the member who created the key, so it sees exactly what that person sees: everything published in the workspace, plus that person's own drafts.
• It can draft a private Skill for that person, and replace one it drafted before.
• It never publishes, never edits published work, and never reaches another member's private work or another workspace.

To give your Talent tools from a server you host or subscribe to, that is the other direction. See Add your own MCP server as a connector.

What to check

• The client shows no talentos tools. Restart it. Most clients read their MCP config only at launch.
• npx: command not found. The launch command needs Node.js on the machine running the client. Install Node, then run the setup command again.
• Every call returns 401. The placeholder key is probably still in place, or the key was revoked. Check the key shows Active under Settings and reads tos_... in full.
• Calls start failing after a burst. Each key allows 60 requests a minute. Pause, then retry after the Retry-After window.
• Reads work but drafting a Skill fails. A workspace whose plan has lapsed is read-only until billing is back in good standing. Reads keep working.
• A workflow you expected is missing. It is probably still a draft owned by someone else. Drafts stay private to their author, including over MCP.