Skip to main content

Overview

The Neuradex MCP server provides 17 tools for LLMs to access Neuradex memory capabilities. For an overview of the MCP integration, see the MCP Overview.
Set an active project with switch_project to omit projectId from other tools.

Project Management

list_projects

Get a list of accessible projects. Parameters: None Return Value:
{
  "projects": [
    {
      "id": "project-abc",
      "name": "Customer Support",
      "note": "Support knowledge base",
      "knowledgeCount": 150,
      "edgeCount": 320
    }
  ]
}
Usage Example:
User: Which projects can I access?

Claude: [Calls list_projects]
        You can access the following projects:
        - Customer Support (knowledge: 150)
        - Internal Wiki (knowledge: 80)

Session Management

switch_project

Set the active project for the current session. After switching, projectId can be omitted from other tools. Parameters:
NameTypeRequiredDescription
projectIdstringNoProject ID
projectNamestringNoProject name (case-insensitive)
Specify either projectId or projectName.
Usage Example:
User: Switch to the Customer Support project

Claude: [Calls switch_project]
        projectName: "Customer Support"

        Switched active project to "Customer Support".
        You can now use tools without specifying projectId.

current_project

Show the currently active project. Parameters: None Usage Example:
User: Which project am I using?

Claude: [Calls current_project]
        Current active project: Customer Support (project-abc)

Knowledge Management

These tools correspond to the Knowledge SDK methods.

create_knowledge

Create a new knowledge entry. Parameters:
NameTypeRequiredDescription
projectIdstringNoProject ID (uses active project if omitted)
titlestringYesTitle
contentstringYesContent
tagsstring[]NoArray of tags
Usage Example:
User: Let's share an agenda before future meetings. Remember this.

Claude: [Calls create_knowledge]
        title: "Meeting Rule: Share Agenda in Advance"
        content: "Share the agenda with participants before holding meetings."
        tags: ["meeting", "rules"]

        Understood. Saved as a meeting rule in knowledge.

search_knowledge

Execute semantic search to find related knowledge. Returns lightweight results (ID, title, tags, score). Parameters:
NameTypeRequiredDescription
projectIdstringNoProject ID (uses active project if omitted)
querystringYesSearch query
limitnumberNoMaximum results (default: 10)
Full content is not included. Use view_knowledge when details are needed.
Usage Example:
User: Tell me about the return policy

Claude: [Calls search_knowledge]
        query: "return policy"

        Found 3 knowledge items related to return policy:
        1. Return Policy (score: 0.92)
        2. Refund Process (score: 0.78)
        3. Exchanges (score: 0.65)

search_agentic

Search across multiple knowledge layers and return a single mixed result list. Filter by type as needed. Parameters:
NameTypeRequiredDescription
projectIdstringNoProject ID (uses active project if omitted)
querystringYesSearch query
limitnumberNoMax total results
perTypeLimitnumberNoMax results per type
includeTypesstring[]NoTypes to include (knowledge / episode / topic / entity / relation)
expandGraphbooleanNoInclude broader related context
maxHopsnumberNoDepth of related context
expandLimitnumberNoSeed count used to broaden results
relationLimitnumberNoMax number of relations
Usage Example:
User: Find last week's authentication discussion and related material

Claude: [Calls search_agentic]
        query: "last week's authentication discussion"
        includeTypes: ["episode", "knowledge", "relation"]
        limit: 12

        Found related episodes, knowledge, and relations in one list.

view_knowledge

View full content of a specific knowledge entry and its connected knowledge. Use this after search_knowledge to get complete details. Parameters:
NameTypeRequiredDescription
projectIdstringNoProject ID (uses active project if omitted)
knowledgeIdstringYesKnowledge ID
Usage Example:
Claude: [Calls view_knowledge]
        knowledgeId: "knowledge-123"

        === Return Policy ===
        Returns are accepted within 30 days of product arrival.

        Return conditions:
        - Item must be unused and unopened
        - Tags must still be attached
        ...

        Related knowledge:
        - Refund Process
        - Shipping Information

list_knowledge

List all knowledge in the project. Useful for browsing and managing the knowledge base. Parameters:
NameTypeRequiredDescription
projectIdstringNoProject ID (uses active project if omitted)
Usage Example:
User: Show me all knowledge in this project

Claude: [Calls list_knowledge]
        Knowledge list for the project:
        1. Return Policy
        2. Shipping Guide
        3. FAQ Collection
        ...(150 total)

update_knowledge

Update an existing knowledge entry’s title and/or content. Parameters:
NameTypeRequiredDescription
projectIdstringNoProject ID (uses active project if omitted)
knowledgeIdstringYesKnowledge ID
titlestringNoNew title (omit to keep current)
contentstringNoNew content (omit to keep current)
Usage Example:
User: Change the return policy deadline to 60 days

Claude: [Calls update_knowledge]
        knowledgeId: "knowledge-123"
        content: "Returns are accepted within 60 days of product arrival..."

        Updated the return policy knowledge.

delete_knowledge

Delete a knowledge entry from the project. Parameters:
NameTypeRequiredDescription
projectIdstringNoProject ID (uses active project if omitted)
knowledgeIdstringYesKnowledge ID
Usage Example:
User: Delete the old return policy knowledge

Claude: [Calls delete_knowledge]
        knowledgeId: "knowledge-456"

        Knowledge deleted.

Context Retrieval

These tools correspond to the Memory SDK methods.

get_context

Get optimized context for a query. Combines semantic search, graph exploration, and episode history to build information for LLMs. Parameters:
NameTypeRequiredDescription
projectIdstringNoProject ID (uses active project if omitted)
querystringYesSearch query
tokenBudgetnumberNoToken limit (default: 4000)
includeEpisodesbooleanNoInclude Q&A history (default: true)
maxDepthnumberNoExploration depth (default: 2, max: 3)
get_context collects information from multiple sources and optimizes to fit within the token budget. Ideal for complex questions.
Usage Example:
User: Tell me about the new deploy flow decided in last week's meeting

Claude: [Calls get_context]
        query: "new deploy flow meeting"
        includeEpisodes: true

        [Collects info from related knowledge + Q&A history]

        Here's a summary of the new deploy flow decided last week:
        1. Auto-deploy to staging when PR is merged
        2. 1-hour canary test on staging
        3. Promote to production if no issues
        ...

Explore related knowledge from a specified entry. Multi-hop exploration discovers knowledge that isn’t directly connected. Parameters:
NameTypeRequiredDescription
projectIdstringNoProject ID (uses active project if omitted)
knowledgeIdstringYesStarting knowledge ID
maxDepthnumberNoExploration depth (default: 2, max: 3)
Usage Example:
Claude: [Calls explore_related]
        knowledgeId: "returns-policy"
        maxDepth: 2

        Explored knowledge related to "Return Policy":

        1 hop (directly related):
        - Refund Process
        - Shipping Information

        2 hops (indirectly related):
        - Payment Methods
        - Customer Support Contact

Episodes (History)

These tools correspond to the Episodes SDK methods.

list_episodes

Search past Q&A history and events. Answers questions like “What was I asked about?” or “Show questions from external users.” Parameters:
NameTypeRequiredDescription
projectIdstringNoProject ID (uses active project if omitted)
timeRangestringNo'today' / 'yesterday' / 'this_week' / 'this_month'
channelstringNo'web' / 'widget' / 'api' / 'mcp' / 'external'
episodeTypestringNo'question' / 'answer'
limitnumberNoMaximum results (default: 20)
Channel filter: web=admin UI, widget=external users, api=API, mcp=MCP, external=external services (Slack, etc.)
Usage Example:
User: What questions were asked this week?

Claude: [Calls list_episodes]
        timeRange: "this_week"
        episodeType: "question"

        This week's questions (10 total):
        - "I want to return a product" (3 times)
        - "Check shipping status" (5 times)
        - "Change payment method" (2 times)

search_topics

Semantic search for topics. Find related topics even with vague queries like “that discussion” or “project progress talk.” Parameters:
NameTypeRequiredDescription
projectIdstringNoProject ID (uses active project if omitted)
querystringYesSearch query
limitnumberNoMaximum results (default: 10)
Usage Example:
User: Find topics about the deploy flow discussion

Claude: [Calls search_topics]
        query: "deploy flow"

        Found 2 related topics:
        1. Deploy Flow Improvement Discussion (score: 0.89)
        2. CI/CD Pipeline Review (score: 0.72)

search_episodes

Semantic search for episodes. Discover past events through semantic search with queries like “password reset” or “last week’s error.” Parameters:
NameTypeRequiredDescription
projectIdstringNoProject ID (uses active project if omitted)
querystringYesSearch query
limitnumberNoMaximum results (default: 10)
Usage Example:
User: Find past conversations about password reset

Claude: [Calls search_episodes]
        query: "password reset"

        Found 3 related episodes:
        1. "How do I reset my password?" (score: 0.95)
        2. "About the password change procedure" (score: 0.82)
        3. "What to do when you can't log in" (score: 0.71)

Librarian (AI Assistant)

These tools correspond to the Librarian SDK methods.

list_librarian_sessions

Get list of Librarian sessions. Parameters:
NameTypeRequiredDescription
projectIdstringNoProject ID (uses active project if omitted)

get_librarian_session

Get Librarian session details (message history). Parameters:
NameTypeRequiredDescription
projectIdstringNoProject ID (uses active project if omitted)
sessionIdstringYesSession ID
formatstringNo'json' / 'yaml' (default: yaml)

Best Practices

Using Session Management

1

First, select a project with switch_project

Setting an active project simplifies subsequent operations
2

Omit projectId from tools

The active project is used automatically
3

Explicitly specify projectId when needed

When you need to access data from a different project
1

First, search with search_knowledge

Get lightweight results and identify relevant knowledge
2

Use view_knowledge for details when needed

When full content of specific knowledge is required
3

Use get_context for complex questions

When you need to gather information from multiple sources

Context Optimization

# For smaller models
get_context(query, tokenBudget: 2000)

# For larger models
get_context(query, tokenBudget: 8000, maxDepth: 3)

Next Steps

SDK Knowledge API

Manage knowledge programmatically

SDK Memory API

Get context programmatically