Skip to content
NeuralRepo
Get Support

Claude AI (MCP)

NeuralRepo integrates with Claude AI through the Model Context Protocol (MCP), allowing Claude to read, create, and manage your ideas directly during a conversation. No copy-pasting, no switching tabs.

The Model Context Protocol is an open standard that lets AI assistants interact with external tools and data sources. When NeuralRepo is connected as an MCP server, Claude gains access to a set of tools for managing your ideas — saving new ones, searching existing ones, linking ideas together, and more.

  1. Open Claude.ai and go to your account settings.

  2. Navigate to the Integrations or MCP Servers section.

  3. Click Add Remote MCP Server and enter the following URL:

    https://neuralrepo.com/mcp/
  4. Save the configuration. On your next conversation, Claude will have access to NeuralRepo tools.

  5. The first time Claude attempts to use a NeuralRepo tool, you will be prompted to authorize via OAuth. Sign in with your NeuralRepo account to grant access.

Once connected, Claude has access to the following tools:

ToolDescription
save_ideaCreate a new idea with title, body, tags, status, source URL, or a parent idea
search_ideasSearch your ideas semantically, or browse them by recency
get_ideaRetrieve a specific idea by ID
update_ideaUpdate an idea’s title, body, status, or tags — one idea, or many at once
delete_ideaArchive an idea by ID (a soft delete)
link_ideasCreate typed relations between ideas — one pair, or a batch (Pro)
unlink_ideasRemove a relation between two ideas (Pro)
list_tagsList all tags with their idea counts
code_modeRun JavaScript against 24 NeuralRepo functions in one call

update_idea and link_ideas each take a bulk form — an ids array and a links array respectively — so Claude can retag or connect a batch of ideas without a call per idea.

code_mode is the one to reach for when a request needs several steps: it exposes a neuralrepo object with functions the eight named tools don’t cover — merging ideas, managing tag colours, adding links, resolving duplicates, and repository stats. See the MCP integration guide.

Once NeuralRepo is connected, you can interact with your ideas naturally in conversation:

You: I just thought of something — we should build a browser extension that highlights text and saves it as an idea. Save this to NeuralRepo.

Claude: I have saved that as a new idea in NeuralRepo. (calls save_idea)

You: Do I have any ideas related to browser extensions?

Claude: Let me check your ideas. (calls search_ideas) You have two related ideas: “Browser extension for bookmarking” and “Chrome plugin for code snippets.”

You: Those two browser extension ideas are related. Link them.

Claude: Done — I have linked them with a “related” relation. (calls link_ideas)

You: Move the habit tracker idea to “building” status.

Claude: Updated. “Build a habit tracker app” is now in the building status. (calls update_idea)

NeuralRepo’s MCP integration uses OAuth 2.0 for secure authorization:

  1. When Claude first attempts to use a NeuralRepo tool, you see an authorization prompt
  2. Clicking Authorize opens the NeuralRepo OAuth consent screen
  3. Sign in with your NeuralRepo account (GitHub, Google, Apple, or magic link)
  4. Grant Claude permission to access your ideas
  5. Authorization is persisted — you do not need to re-authorize for future sessions

Two scopes exist: ideas:read and ideas:write. Anything that changes data — save_idea, update_idea, delete_idea, link_ideas, unlink_ideas, and code_mode — is refused without ideas:write.

  • MCP access is read-write — Claude can create, update, and archive ideas on your behalf. Review Claude’s actions if you want to be cautious.
  • The link_ideas and unlink_ideas tools require a Pro plan; everything else works on Free.
  • Semantic search is limited to 10/month on Free, after which search_ideas returns keyword results with a notice.
  • On Free, save_idea refuses once you hold 50 active ideas.
  • Rate limits apply: Free allows 100 requests/day, Pro allows 10,000 requests/day, reset at midnight UTC. Every MCP call counts.