Bhived MCP
Connect agents to Bhived’s shared knowledge graph plus skills and tool discovery so multiple workflows pull the same organizational memory.
Overview
Bhived MCP is a Build-phase MCP server that connects agents to Bhived’s shared knowledge graph, skills, and tool discovery over stdio npm.
What is this MCP server?
- stdio npm package bhived-mcp v1.1.10 with required secret BHIVED_API_KEY
- Authenticate via npx bhived auth or paste an API key from your Bhived account
- Exposes shared knowledge graph access for cross-session agent memory
- Includes skills and tool discovery surfaces for MCP-capable clients
- GitHub source ArtKeyAi/bhived-mcp for Model Context Protocol wiring
- npm package bhived-mcp version 1.1.10
- Required environment variable BHIVED_API_KEY
- Transport stdio via npm registry
Community signal: 20 GitHub stars.
What problem does it solve?
Solo builders juggling multiple agents lose shared context because notes and skills sit in silos instead of one queryable graph.
Who is it for?
Small teams already on Bhived who want Claude Code or Cursor to reuse the same graph-backed memory during implementation.
Skip if: Builders who only need local file search or who will not run Bhived auth and API key management.
What do I get? / Deliverables
After registration, agents pull consistent Bhived knowledge and discover relevant skills or tools without re-scraping scattered docs.
- Graph-backed answers and references inside agent sessions
- Discovered Bhived skills and tools aligned to current tasks
- Shared knowledge layer reused across multiple agent workflows
Recommended MCP Servers
Journey fit
Builders wire external knowledge systems during Build when the product and agent stack need a durable integration, not a one-off spreadsheet. Integrations is the canonical home for MCP servers that bridge a third-party knowledge platform into the agent runtime.
How it compares
Bhived platform bridge via MCP, not a generic filesystem indexer or a single-repo Claude skill.
Common Questions / FAQ
Who is Bhived MCP for?
Solo and indie builders standardizing on Bhived for team knowledge who want MCP agents to read the graph and discover skills during development.
When should I use Bhived MCP?
Use it when you start wiring agent workflows in Build and need shared, updatable knowledge plus tool discovery instead of copying context into every chat.
How do I add Bhived MCP to my agent?
Install npm package bhived-mcp, set BHIVED_API_KEY (run npx bhived auth or use a dashboard key), add the stdio server to your MCP config, and restart the client.