MCP with Claude Code

1. Step 1 / 9

   Welcome

   You're about to register the Deep Thought MCP server with Claude Code. After this, in any terminal session where you run claude, you can ask about your meetings, notes, transcripts, and entities — and Claude reads them directly through MCP.

   This is the remote MCP connector: Claude Code talks to mcp.deep-thought.cloud over HTTPS using OAuth 2.1. The first call triggers a browser pop-up for consent (one-time), then Claude Code remembers the token. You can revoke at any time.

   What you'll do in the next 5 minutes

   • Verify Claude Code is installed
   • Register the Deep Thought server with claude mcp add
   • Trigger the first call (the browser opens for OAuth)
   • Verify the response includes citations from your knowledge base

2. Step 2 / 9

   Verify Claude Code is installed

   Open a terminal and run:

   claude --version

   You should see a version string like 1.x.y. If you get command not found, install Claude Code first from claude.ai/code — there's a single-line install script on that page.

   Then check what MCP servers you already have:

   claude mcp list

3. Step 3 / 9

   Register the Deep Thought server

   Run this command in your terminal:

   claude mcp add dt-cloud --transport http https://mcp.deep-thought.cloud/mcp

   Breakdown:

   • dt-cloud — the name you'll see in claude mcp list. Pick anything memorable; dt-cloud is the convention.
   • --transport http — Streamable HTTP transport.
   • https://mcp.deep-thought.cloud/mcp — the production Deep Thought MCP endpoint.

   Verify it's registered:

   claude mcp list

   You should see dt-cloud listed alongside any existing servers.

4. Step 4 / 9

   Make the first call — OAuth triggers

   Start a Claude Code session (anywhere — your home directory works):

   claude

   Then prompt:

   List my Deep Thought sources via the dt-cloud MCP server.

   Claude Code will try to call a tool from dt-cloud. Because this is the first call, it needs to authenticate. Claude Code opens a browser window pointing at https://app.deep-thought.cloud/oauth/consent.

   If the browser doesn't open automatically, look for a URL in Claude Code's output and open it manually.

5. Step 5 / 9

   Approve scopes in the browser

   On the consent page:

   • Sign in with your Deep Thought account if not already
   • Review the scopes Claude Code is asking for:
     • kb:read — read sources, transcripts, summaries, entities
     • graph:read — traverse the entity graph
     • kb:write (optional) — lets Claude create action items (create_action) and write the note on a source (set_source_note), the two tools that write

   Click Approve. The page redirects back, and Claude Code's first tool call completes. You'll see the result in your terminal.

   The token is stored by Claude Code in its config — you won't be prompted again for this server unless you revoke or move machines.

6. Step 6 / 9

   Try a real query

   In the same Claude Code session, try something specific:

   Search my Deep Thought knowledge for the last planning meeting we had this month. Summarise the decisions.

   Or:

   What entities are connected to [a person or project name you've discussed]?

   Claude Code will pick the right MCP tool (search, get_entity, get_entity_neighborhood) and call it. You may see Claude announce "I'll search your Deep Thought knowledge…" before responding.

7. Step 7 / 9

   Verify the response cites real data

   Claude's response should reference specific sources — meeting titles, source IDs, dates, entity names you recognize. If the answer is generic and doesn't mention anything from your actual knowledge base, something didn't connect.

   If you see citations: the connector works. You're done.

   If the response is generic:

   • Run claude mcp list and confirm dt-cloud is there
   • Re-trigger by asking Claude to explicitly use the dt-cloud server for the search
   • Check Claude Code didn't fall back to other connectors / web search
   • If still stuck: claude mcp remove dt-cloud then re-add and re-authorize
   • Or email support@deep-thought.cloud

8. Step 8 / 9

   How to revoke the connection

   Two paths:

   From Deep Thought (recommended — invalidates immediately)

   Visit app.deep-thought.cloud/settings/devices. You'll see a list of connected MCP clients (one per machine where you set up dt-cloud). Click Revoke next to any entry — the device token is invalidated server-side instantly. Claude Code's next call will get a 401.

   From Claude Code (removes local config)

   claude mcp remove dt-cloud

   This deletes the entry locally. The token stays valid server-side until it expires (or you revoke it from the Deep Thought side too).

   Best practice: revoke from Deep Thought first (invalidates the token), then remove from Claude Code (cleans up the local config).

9. Step 9 / 9

   Done

   Claude Code can now read your Deep Thought knowledge from any terminal. Run claude in any project directory and ask questions in plain English — Claude will pick the right MCP tool and answer with citations.

   Patterns that work well

   • Daily standup prep. "What did we decide in yesterday's standup?" → Claude pulls the source, lists decisions and action items.
   • Codebase + knowledge. "This file references the 'foo' service — what did we discuss about it in the architecture meeting?" → Claude combines code-reading with MCP.
   • Action-item harvest. "List every open action assigned to me, grouped by project." → Claude reads actions from Deep Thought directly.

   Going deeper

   • Read about the full MCP product — all 20 tools, scopes, capabilities
   • Add Claude Desktop too if you want chat-style access alongside the terminal

If you get stuck, e-mail support@deep-thought.cloud. All guides