Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.thor.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
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, 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 support@thor.ai.
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.
In Cursor, ask: “Use Thor to find all conversations and relevant context for issue #123 — related Slack threads, meeting decisions and recent activity — then include those in your proposed code plan.”

​
Standup summaries and daily briefings

Skip the context switch to Slack. Ask your MCP client to fetch your standup or daily briefing directly:
In Claude or Cursor: “Get my Thor standup for today and call out what needs my attention today.”

​
Keep your project management system up-to-date

If you’re heads-down in your editor and need to update Linear with your prgoress, your MCP client can post it back to Thor:
In Cursor: “Update Linear to reflect that I’m working on issue #123 and where the latest blocker is.”