Autoplans MCP Server
What We've Built
This repo contains everything needed to publish your Autoplans.dev MCP server to the official registry:
server.json - MCP Registry manifest using latest 2025-10-17 schema
package.json - npm package configuration
index.js - stdio wrapper that proxies to your HTTP API
mcp.json - Original manifest (kept for reference)
How It Works
Your server runs as HTTP at https://autoplans.dev/api/v1/mcp, but the MCP Registry expects stdio-based packages. Our wrapper solves this by:
- Publishing an npm package that provides stdio transport
- Proxying MCP stdio calls to your HTTP API
- Requiring users to set
AUTOPLANS_API_KEY environment variable
- Enabling discovery through the official MCP Registry
Publishing Status
Installation & Usage
npm install -g autoplans-mcp
export AUTOPLANS_API_KEY="your_api_key_here"
autoplans-mcp
Quick Setup for Popular Editors
VS Code / Cursor:
{
"mcp.servers": {
"autoplans": {
"command": "npx",
"args": ["autoplans-mcp"],
"env": {
"AUTOPLANS_API_KEY": "your_api_key_here"
}
}
}
}
Claude Desktop:
{
"mcpServers": {
"autoplans": {
"command": "npx",
"args": ["autoplans-mcp"],
"env": {
"AUTOPLANS_API_KEY": "your_api_key_here"
}
}
}
}
📖 Complete Installation Guide - Detailed setup for all editors
Publish steps
Initialize git and push to GitHub (example):
git init
git add .
git commit -m "Initial MCP manifest and README"
git branch -M main
git remote add origin https://github.com/msaid/autoplans-mcp.git
git push -u origin main
Install the MCP Publisher CLI (example on macOS using Homebrew):
brew install mcp-publisher
Authenticate with the MCP registry:
mcp-publisher login
Publish the manifest (run from the repo root where mcp.json lives):
mcp-publisher publish ./mcp.json
The registry will register your server and make the listed tools discoverable.
Updating / Releasing
- Bump the
version field in mcp.json.
- Commit and push the change to GitHub.
- Run
mcp-publisher publish ./mcp.json again to update the registry pointer.
Security & Auth
mcp.json in this repo indicates bearer auth for clients (API keys in Authorization header).
- Ensure your server validates and scopes API keys correctly.
API Examples
Get all available tools:
curl -X POST "https://autoplans.dev/api/v1/mcp" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list",
"params": {}
}'
Call a tool (list projects):
curl -X POST "https://autoplans.dev/api/v1/mcp" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "list_projects",
"arguments": { "limit": 5 }
}
}'
Available Tools (14+)
- Projects:
list_projects, create_project, get_project
- Tasks:
create_task, list_tasks, get_task, update_task, delete_task
- Bulk Operations:
bulk_update_tasks, bulk_create_tasks
- Business Plans:
get_business_plan, create_business_plan
- Branding:
get_branding, create_branding
Ready to Publish!
Your MCP server is fully functional and the manifest is complete. To publish to the official MCP registry:
- Push to GitHub: Run the git commands above
- Install MCP Publisher:
brew install mcp-publisher (or download for your OS)
- Authenticate:
mcp-publisher login
- Publish:
mcp-publisher publish ./mcp.json
Get Your API Key
Users need their own API key from https://autoplans.dev to use these tools.
Need Help?