autonomous-loop
Iterate until success or limit, composing existing skills with Jidoka integration
Guide for creating new MCP server integrations
$ npx -y skills add WellApp-ai/Well --skill mcp-server --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/mcp-serverContext preview
The summary Claude sees to decide when to auto-load this skill.
Guide for creating new MCP server integrations
name: mcp-server description: Guide for creating new MCP server integrations
Use this skill when creating a new MCP server integration.
MCPs live in: `~/.cursor/projects/<project>/mcps/<server-name>/`
mcps/
├── user-notion/
│ └── tools/
│ ├── API-retrieve-a-page.json
│ └── ...
├── cursor-ide-browser/
│ └── tools/
│ ├── browser_navigate.json
│ └── ...
└── user-n8n-mcp/
└── tools/
└── ...Each tool is a JSON file:
{
"name": "tool-name",
"description": "What this tool does",
"arguments": {
"type": "object",
"properties": {
"param1": { "type": "string", "description": "..." }
},
"required": ["param1"]
}
}1. Read tool descriptor before calling 2. Use `CallMcpTool` with server, toolName, arguments 3. Handle response appropriately
CallMcpTool:
server: "user-notion"
toolName: "API-retrieve-a-page"
arguments: { "page_id": "abc123" }| MCP | Capabilities | |-----|--------------| | **user-notion** | Page/block CRUD, search, comments | | **cursor-ide-browser** | Navigation, clicks, screenshots, console | | **user-n8n-mcp** | Workflow search, details, execution | | **user-context7** | Library docs lookup | | **figma** | Design specs, code generation from frames |
1. Create folder: `mcps/<server-name>/tools/` 2. Add tool descriptors as JSON files 3. Configure server in `~/.cursor/mcp.json` 4. Restart Cursor (Cmd+Shift+P > "Reload Window") 5. Test with `CallMcpTool`
For MCPs that use API keys (Notion, n8n):
"mcp-name": {
"command": "npx",
"args": ["-y", "@package/mcp-server"],
"env": {
"API_KEY": "your-token-here"
}
}For MCPs that connect to local servers (Figma desktop):
"mcp-name": {
"url": "http://127.0.0.1:PORT/mcp"
}For MCPs that use browser OAuth (Figma remote):
"mcp-name": {
"url": "https://service.com/mcp"
}After adding, click "Connect" in Cursor MCP settings to authorize.
**Installation loops infinitely:**
**MCP not appearing:**
Iterate until success or limit, composing existing skills with Jidoka integration
Generate and maintain BPMN 2.0 diagrams linked to Gherkin scenarios
Research best-in-class products using Browser MCP and WebSearch
Systematic debugging with MCP integration, auto-invoke from qa-commit, Phase 7 Harden