An MCP server for the Story SDK and Storyscan Block Explorer
If you already use Story SDK, the story sdk mcp server is the piece that lets your assistant work with it directly. An MCP server for the Story SDK and Storyscan Block Explorer.
This repository serves as a central hub for Story Protocol's Model Context Protocol (MCP) servers. It provides a unified environment for running and managing various MCP services that enable AI agents to interact with Story Protocol's ecosystem.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Prerequisites — The Prerequisites tool exposed by this serverInstallation — The Installation tool exposed by this serverCursor — Cursor implements an MCP client that supports an arbitrary number of MCP servers with both stdio and sse transportsTroubleshooting — 1. Verify that environment variables are set correctly for each server 2. Check network connectivity to external APIs (StoryScan, IPFS, etc.) 3Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Story SDK's toolset — Prerequisites, Installation, Cursor and 1 more — is a fair guide to whether it matches your workflow. It is maintained by piplabs; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | The Installation tool exposed by this server. |
| Cursor | Cursor implements an MCP client that supports an arbitrary number of MCP servers with both stdio and sse transports. |
| Troubleshooting | 1. Verify that environment variables are set correctly for each server 2. Check network connectivity to external APIs (StoryScan, IPFS, etc.) 3. Ensure you're using the correct Python version (3.12+) 4. Check that all de |
{
"mcpServers": {
"storyscan-mcp": {
"command": "uv",
"args": [
"--directory",
"~/path/to/story-mcp-hub/storyscan-mcp",
"run",
"server.py"
]
},
"story-sdk-mcp": {
"command": "uv",
"args": [
"--directory",
"~/path/to/story-mcp-hub/story-sdk-mcp",
"run",
"server.py"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.