Where it fits
Neuroscience researchers and data teams working with knowledge graph ingestion, querying, provenance, and entry management.
- Ingest data into the BrainKB neuroscience knowledge graph.
- Query BrainKB graphs and PROV-O provenance.
- Check the status of ingest jobs.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with BrainKB
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Dispatches one agent per independent problem domain so unrelated failures can be investigated concurrently, then reviews and integrates the results. Use it when failures are separate, need no shared context, and can run without interfering.
For carrying out an implementation plan inside the current session, with the agent acting as the implementer itself. That happens when the human partner picked inline execution or when no subagent tool is available.
Helps decide how to integrate finished work after implementation and passing tests. Presents structured choices for merging locally, pushing and creating a pull request, or keeping the branch.
No skills found
Try a different search term or clear the filters.
Local stdio server
Clone the repository, install requirements, then run the stdio server with your BrainKB credentials. The hosted https://mcp.brainkb.org/mcp endpoint is documented as a later release, not a current install path.
- Clone and install
Follow the repository README to create a virtual environment and install requirements.
pip install -r requirements.txt - Run the stdio server
Start the server locally. It exposes tools over stdio and uses your BrainKB account session.
python server.py - Register it in your client
Point your MCP client at the Python executable and server.py, then sign in with your BrainKB account.
This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
- The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
- The client cannot find the vomo command. Confirm the global CLI install and that the executable is on PATH.
- The process starts but no tools appear. Sign in to the provider CLI, restart the client, and check the local command output for errors.
Before you connect
- The MCP server process runs on your machine, not on a provider host.
- Data leaves only through the model provider and any MCP servers you attach.
- Review the local command, package, and files it can reach before running it.
- Stop the process or remove the client entry when you no longer need it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider source
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
BrainKB repositoryhttps://github.com/sensein/brainkb_mcp