Honcho MCP Server: Setup for Claude, Cursor and Other Apps

• Asks a question about one person and gets a reasoned answer

  Asks Honcho's reasoning system a question about a single peer, such as a user, and returns an answer built from what it has learned. You can limit it to a session or scope.

  Try: “What does this user prefer when we talk about code reviews?”

  Network · chat

• Asks a question across everything in a workspace

  Asks a natural-language question about the whole workspace and returns an answer from Honcho's reasoning system.

  Try: “What topics came up most across all my conversations?”

  Network · workspace_chat

• Searches messages and saved facts by meaning

  Runs a semantic search across messages, and also across a peer's saved conclusions when you name a peer.

  Try: “Find where we discussed the pricing change.”

  Network · search

• Gets everything Honcho knows about a peer in one go

  Combines a peer's conclusions and peer card into one context block.

  Try: “Load my full context before we start.”

  Network · get_peer_context

• Shows the short fact sheet about a peer

  Returns the peer card, a compact list of biographical facts.

  Try: “Show my peer card.”

  Network · get_peer_card

• Sets or updates the fact sheet about a peer

  Writes the peer card, a list of facts about the peer.

  Try: “Update my peer card: I work in Berlin and prefer TypeScript.”

  Write · set_peer_card

• Shows a text summary of what Honcho knows about a peer

  Returns a formatted summary built from the peer's conclusions, optionally limited to a session or scope.

  Try: “Give me the current summary of what you know about this user.”

  Network · get_representation

• Creates a peer, or returns it if it exists

  Gets or creates a peer, which is a person or agent that Honcho remembers things about.

  Try: “Create a peer called alice.”

  Write · create_peer

• Lists the peers in a workspace

  Lists peers in the workspace, with paging.

  Try: “Who does Honcho know about in this workspace?”

  Network · list_peers

• Lists the workspaces your key can reach

  Lists workspaces that the current credentials can access, with paging.

  Try: “Which Honcho workspaces do I have?”

  Network · list_workspaces

• Creates a workspace, or returns it if it exists

  Gets or creates a workspace with the ID you give.

  Try: “Create a workspace called support-bot.”

  Write · create_workspace

• Shows a workspace at a glance

  Aggregates metadata, configuration and the peer and session IDs of a workspace.

  Try: “Give me an overview of the support-bot workspace.”

  Network · inspect_workspace

• Reads metadata of a workspace, peer or session

  Returns metadata for a resource, depending on which IDs you pass.

  Try: “Show the metadata of session s-12.”

  Network · get_metadata

• Replaces metadata on a resource

  Sets metadata for a resource and overwrites what was there.

  Try: “Set the metadata of session s-12 to topic=billing.”

  Write · set_metadata

• Starts a conversation session, or returns it if it exists

  Gets or creates a session, optionally joining scopes at creation.

  Try: “Create a session for today's planning call.”

  Write · create_session

• Lists sessions in a workspace

  Lists sessions with paging.

  Try: “List my recent sessions.”

  Network · list_sessions

• Saves messages into a session

  Adds messages to a session from specific peers. Honcho learns from them over time.

  Try: “Save this conversation to session s-12 as messages from me and the assistant.”

  Write · add_messages_to_session

• Reads the messages in a session

  Returns the messages of a session, with paging and optional metadata filters.

  Try: “Show the messages in session s-12.”

  Network · get_session_messages

• Reads one message from a session

  Returns a single message by ID.

  Try: “Show message m-88 from session s-12.”

  Network · get_session_message

• Builds ready-to-use context for a session

  Returns session context suited for model prompts, and can include a peer's representation and card.

  Try: “Load the context of session s-12 so we can continue.”

  Network · get_session_context

• Shows a session at a glance

  Summarizes a session.

  Try: “Give me an overview of session s-12.”

  Network · inspect_session

• Lists who is in a session

  Returns the peers taking part in a session.

  Try: “Who is in session s-12?”

  Network · get_session_peers

• Adds peers to a session

  Adds one or more peers to a session.

  Try: “Add bob to session s-12.”

  Write · add_peers_to_session

• Removes peers from a session

  Removes one or more peers from a session.

  Try: “Remove bob from session s-12.”

  Write · remove_peers_from_session

• Copies a session, optionally up to a message

  Clones a session, optionally only up to a given message.

  Try: “Clone session s-12 up to message m-40.”

  Write · clone_session

• Deletes a session and all its messages

  Deletes a session together with every message in it.

  Try: “Delete session s-12.”

  Delete · delete_session

• Lists scopes in a workspace

  Lists scopes, which group sessions, with paging.

  Try: “What scopes exist?”

  Network · list_scopes

• Creates a scope, or returns it if it exists

  Gets or creates a scope with the ID you give.

  Try: “Create a scope called work-chats.”

  Write · create_scope

• Puts sessions into a scope

  Adds existing sessions to a scope. Re-adding one does nothing.

  Try: “Add sessions s-12 and s-13 to work-chats.”

  Write · add_sessions_to_scope

• Takes a session out of a scope

  Removes a session from a scope.

  Try: “Remove s-13 from work-chats.”

  Write · remove_session_from_scope

• Lists the sessions in a scope

  Lists sessions that belong to a scope, with paging.

  Try: “Which sessions are in work-chats?”

  Network · get_scope_sessions

• Shows how far a scope has been processed

  Returns backfill progress for a scope, per session.

  Try: “Is work-chats done processing?”

  Network · get_scope_status

• Lists the facts Honcho has learned about a peer

  Lists the conclusions (facts and observations) derived about a peer, with paging.

  Try: “What has Honcho learned about me?”

  Network · list_conclusions

• Searches the facts Honcho has learned

  Runs a semantic search across a peer's conclusions.

  Try: “What do you know about my travel plans?”

  Network · query_conclusions

• Fetches conclusions by ID

  Fetches conclusions by ID, which also shows the facts a conclusion was derived from.

  Try: “Show where conclusion c-9 came from.”

  Network · get_conclusions

• Shows what was built on top of a fact

  Lists conclusions derived from a given conclusion. Useful before correcting or deleting a fact.

  Try: “What depends on conclusion c-9?”

  Network · get_derived_conclusions

• Adds facts about a peer by hand

  Creates conclusions that were not derived from conversation.

  Try: “Remember that I am allergic to peanuts.”

  Write · create_conclusions

• Deletes a learned fact

  Deletes a conclusion by ID. Use it to remove incorrect or outdated knowledge.

  Try: “Delete conclusion c-9, it is wrong.”

  Delete · delete_conclusion

• Triggers background memory cleanup for a peer

  Schedules a dream, a background task that consolidates a peer's memory.

  Try: “Run a memory consolidation for me.”

  Write · schedule_dream

• Shows what Honcho is still processing

  Returns the status of the background queue for message processing and dreams.

  Try: “Is Honcho still processing my last messages?”

  Network · get_queue_status

Watch out for

• It can delete sessions and facts

  Deleting a session removes all its messages, and a delete tool removes learned facts. Use a separate workspace for experiments. github.com

• Conversations are stored by a third party

  Messages you add go to Honcho, which derives facts and profiles from them. Do not save passwords or private data. github.com

• One key reaches the whole workspace

  The API key is sent as a Bearer header and covers every tool. Keep it out of shared config files. github.com

• Requests can take a long time

  The README says chat calls can run up to 5 minutes by default, which can stall a client. github.com

Security advisories