@superlayer/mcp
v2.0.0
Published
Model Context Protocol (MCP) server for managing Superlayer apps, schemas, and permissions!
Readme
@superlayer/mcp
Model Context Protocol (MCP) server for managing Superlayer apps, schemas, and permissions!.
Maintained by Superlayer. See LICENSE.md and NOTICE for upstream attribution.
Welcome to Superlayer’s MCP server.
Superlayer MCP
This MCP is a wrapper around the Superlayer Platform SDK. Add this MCP to your editor to enable creating, managing, and updating your Superlayer applications.
Remote MCP server
Superlayer hosts the latest version of the server at https://mcp.interfacedb.com.
For modern clients that support streamable HTTP use https://mcp.interfacedb.com/mcp.
For legacy clients that require SSE use https://mcp.interfacedb.com/sse.
For more editor-specific instructions, see the public docs.
Local MCP server
If you haven't already, make sure to get a personal access token from your Superlayer dashboard.
Run the server in stdio mode with npx -y @superlayer/mcp --token <token>.
For more editor-specific instructions, see the public docs.
Contributing
Quick Start
Clone this repo and use the MCP Inspector @modelcontextprotocol/inspector to debug and
develop against this server locally.
# Clone this repo
git clone ..
# Navigate to the cloned directory and build the MCP server
cd ..
npm run build
# Run the server
npx @modelcontextprotocol/inspector node ./dist/index.js --token <token>
# Or alternatively via environment variable
SUPERLAYER_ACCESS_TOKEN=<token> npx @modelcontextprotocol/inspector node ./build/index.js
# You can also specify a url to connect to a local instance of your Superlayer server
npx @modelcontextprotocol/inspector node ./dist/index.js --token <token> --api-url
http://localhost:8888If you're using Claude Code you can add the mcp server directly after building:
claude mcp add --transport stdio superlayer-local -- node <path-to-your-cloned-repo>/dist/index.js --token <token>You can then remove the server directly:
claude mcp remove superlayer-localYou can also configure your editor to connect to your local MCP. Here's an example configuration for MacOS/Linux:
{
"mcpServers": {
"superlayer": {
"command": "node",
"args": [
"<path-to-your-cloned-repo>/dist/index.js",
"--token",
"<token>",
"--api-url",
"http://localhost:8888"
]
}
}
}Remote MCP
cp .env.example .envFill in all of the environment variables for your new .env file.
pnpm run devVisit the server at http://localhost:3123.
To work on the stdio version of the codebase, update your .env file with SERVER_TYPE=stdio.
