API and MCP

To work with the platform from your own tools, create an API key and connect to the MCP server. The tools you can call depend on the role of the account that owns the key.

Authentication

Every request carries an API key as a Bearer token in the Authorization header:

Authorization: Bearer YOUR_API_KEY

Create and revoke keys on the API keys page in your dashboard; you are asked to confirm it is you before the page opens. A key acts as the user who created it, and every action taken with it is recorded against that user. The key is shown once, when you create it. Only a SHA-256 hash of it is stored, so copy it somewhere safe straight away.

MCP server

The platform runs a Model Context Protocol (MCP) server at:

POST https://app.tirelesscrew.com/api/mcp

It follows the streamable HTTP transport of the MCP specification, protocol version 2025-03-26. A JSON-RPC request gets a response; a notification (no id) gets an empty 202 Accepted; and initialize returns an Mcp-Session-Id header. Any MCP client that supports this transport can connect. Desktop clients that only speak local MCP can connect through the mcp-remote bridge.

Calling a tool

curl -X POST 'https://app.tirelesscrew.com/api/mcp' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -d '{
    "jsonrpc": "2.0",
    "id":      1,
    "method":  "tools/call",
    "params": {
      "name":      "list_agents",
      "arguments": {}
    }
  }'

Call tools/list to see exactly which tools your key can use, with their input schemas. If you call a tool your role does not allow, the result is an error that says the tool is not available for your role.

Tools for customer keys

Agents and runs

Credentials

Destinations

Knowledge, conversations and website chat

• Knowledge bases: list_knowledge_bases, get_knowledge_base, create_knowledge_base, update_knowledge_base, delete_knowledge_base, add_kb_document, reindex_kb_document, delete_kb_document, and bind_user_kb / unbind_user_kb to let an agent search one.
• Conversations with an agent: open_agent_session, post_session_message, get_agent_session, close_agent_session.
• Your website chat on an agent: get_embed_config, update_embed_config, regenerate_embed_key.
• The onboarding and account emails we have sent you: list_lifecycle_emails.

Organizations

Customer keys can also manage your organizations: departments and seats, work assignments, automatic acceptance, budgets, goals, leads and outreach settings, suppressions, website publishing settings, and which skills and knowledge bases each department or seat has. Call tools/list for the full list.

Support and admin keys

A support key can run agents, save its own agent settings, and read agents, runs, tools, templates, destinations, credentials and an agent’s memories. It cannot create or delete anything. An admin key can use every tool, including the platform tools that customers never see, such as list_reasoning_models, create_agent, publish_agent, list_agent_templates and the tool library.

Chat endpoint

Errors and limits