MCP Server

Connect Thor to Cursor, Claude and other MCP-compatible clients to use Thor as the data source for your AI workflows.

What is the Thor MCP server?

Thor’s Model Context Protocol (MCP) server exposes Thor’s capabilities to any MCP-compatible AI client — including Cursor, Claude Desktop, and custom integrations.

Instead of building and maintaining your own multi-MCP data pipeline that stitches together GitHub, Linear, calendar, meeting transcripts, Slack and more, you can point your AI client at a single endpoint. Thor handles the cross-tool reasoning, permissions and context for you, so the answers your coding agent or chat client gets are faster, cheaper, more accurate and more reliable.

What you can do with it

Once connected, your MCP client gets access to Thor’s core capabilities:

• Ask Thor any question it can already answer in Slack — about issues, projects, documents, teams, meetings and decisions.
• Pull your daily standup summary (or a teammate’s, with the right permissions) directly into your editor or chat.
• Add notes, blockers and updates to your standup without leaving your editor.

Connect your client

Cursor, Claude Code, and any other MCP-compatible client connect to Thor the same way: add a Thor entry to your client’s mcp.json configuration file pointing at your organization’s Thor MCP URL.

{
  "mcpServers": {
    "Thor": {
      "type": "http",
      "url": "https://<tenant>.thor.ai/mcp"
    }
  }
}

Replace <tenant> with app or your single-tenant subdomain name. If you’re not sure what your URL is, contact [e-mail].

Some clients, like Claude Desktop, don’t fully support standardized http/oauth connections yet. If you use Claude Desktop, or the config above doesn’t work for you, you can install mcp-remote and use the following config instead:

{
  "mcpServers": {
    "Thor": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://<tenant>.thor.ai/mcp"
      ]
    }
  }
}

The first time your client connects, you’ll be redirected through an OAuth flow — sign in with the Slack account you use for Thor. There are no API keys to manage.

Authentication and permissions

The MCP server resolves your identity from your OAuth login and applies the same organization and channel permissions as the Thor Slack app — you’ll only see data you already have access to in Thor.

Use cases

Pull team context into your coding agent

When delegating a task to a coding agent (see Tasks → Delegate to coding agents), the agent can use Thor over MCP to load the full context for the issue — related discussions, prior decisions in meetings, linked PRs, and recent activity from teammates working on adjacent code.

Standup summaries and daily briefings

Skip the context switch to Slack. Ask your MCP client to fetch your standup or daily briefing directly:

Keep your project management system up-to-date

If you’re heads-down in your editor and need to update Linear with your progress, your MCP client can post it back to Thor: