Claude Code
Run this from the project you want Arkweaver connected to.
claude mcp add --transport http arkweaver https://mcp.arkweaver.com/mcp \
--header "Authorization: Bearer YOUR_TOKEN"Arkweaver MCP
Connect Arkweaver to Claude, Cursor, or Codex over MCP. Ask which feature is blocking a deal. Spin up a battlecard. Check when a customer's must-have ships. Every answer comes from your own calls.
Included on every plan. Six tools, read-only by default, live in about two minutes.
Which missing features are blocking open deals?
Three come up in open pipeline this quarter:
Want a battlecard for the SSO objection?

What you can ask
Every answer is grounded in your own conversations. The accounts and the quotes come with it.
Which missing features are blocking open deals?
Build me a sales battlecard for the SSO objection.
When is bulk export due, and who is waiting on it?
Which closed-lost deals can I reopen based on what we shipped last quarter?
What did we ship last month, and which accounts asked for it?
Draft outreach to everyone waiting on SSO.
Setup
In Arkweaver, go to Settings → MCP setup and generate an access token. It is shown once, so copy it before you leave the page.
Find your client below and run its setup, pasting your token in place of YOUR_TOKEN.
Restart your client, then check that arkweaver appears in its list of connected MCP servers. Ask it what your top feature requests are.
Run this from the project you want Arkweaver connected to.
claude mcp add --transport http arkweaver https://mcp.arkweaver.com/mcp \
--header "Authorization: Bearer YOUR_TOKEN"Add this to ~/.codex/config.toml, then set ARKWEAVER_MCP_TOKEN to your token.
[mcp_servers.arkweaver]
url = "https://mcp.arkweaver.com/mcp"
bearer_token_env_var = "ARKWEAVER_MCP_TOKEN"Add this to ~/.cursor/mcp.json.
{
"mcpServers": {
"arkweaver": {
"url": "https://mcp.arkweaver.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}Any MCP client with remote servers and bearer-token auth will work. These three are the ones we test against.
Tool reference
Three answer questions. One drafts deliverables. Two are plumbing your assistant calls on its own. You never pick one by hand.
search_product_intelligence ReadBroad questions about what customers want, which features matter, and which product lines exist. Returns ranked product lines and features.
Inputs query, limit
get_feature_context ReadEverything Arkweaver knows about one feature. Who asked, what they said, current status, linked issues. Resolves fuzzy phrasing, ticket IDs, and labels.
Inputs feature_id or query
query_extracted_insights ReadRanked features, product lines, and supporting evidence quotes for open-ended product-intelligence questions.
Inputs query, limit
list_templates ReadThe deliverable templates your team can generate from. One-pagers, battlecards, launch FAQs, positioning, GTM briefs.
Inputs query
create_product_deliverable WriteQueues a deliverable for a feature or product line from an existing template. Reuses a recent matching deliverable by default rather than duplicating work.
Inputs target_type, target_id or query, template_query, creation_mode
get_report_job ReadChecks whether a queued deliverable has finished and where to open it.
Inputs report_job_id
Boundaries

The MCP reads extracted records. Features, requesters, evidence quotes. It does not search or return full call transcripts.
No tool sends an email, Slack message, or customer outreach. Deliverables are queued as drafts inside Arkweaver for a human to review.
Features already Built and announced are excluded from demand rankings unless your question names them directly.
Your token sees exactly what your Arkweaver account sees. Your group's data and nothing else.
Access & security
Each token belongs to one Arkweaver account and carries that account's permissions. It is stored hashed. We cannot show it to you again after it is generated.
Generating a new token immediately invalidates the previous one. Rotate from Settings → MCP setup. The old token stops working that second.
The MCP reads your group's Arkweaver records over an encrypted connection. Conversation data is never shared across customers or used to train shared models.
Every answer and deliverable your sales team needs to close. Ask Arkweaver. Get it in seconds.