Menü
Guide for creating new MCP server integrations
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Connect and verify the Well MCP — authenticate, confirm the tools work, and show what to ask. Use when the user runs /well:connect, just installed the Well plugin, or says the Well connection/MCP "isn't working" / "nothing happened".
Produce an accounts-receivable aging report and surface overdue invoices for a Well workspace. Use when the user asks who owes them money, an AR aging report, overdue invoices, days sales outstanding (DSO), or which customers to chase.
Forecast cash flow and runway for a Well workspace from booked invoices and collected bank transactions. Use when the user asks for a cash-flow forecast, runway, how long until they run out of cash, projected balance, or expected inflows/outflows.
Run a month-end (or period) close checklist against a Well workspace — verify everything is reconciled and posted before the books are closed. Use when the user asks to close the month/period, run a close checklist, check if the books are ready to close, or what's left before closing.
Produce a VAT / sales-tax summary for a period from a Well workspace's posted ledger. Use when the user asks for a VAT return, VAT summary, sales tax owed, output vs input VAT, or tax declaration figures for a period.
Build a balance sheet (bilan) from a Well workspace. Use when the user asks for a balance sheet, bilan, assets/liabilities/equity, or financial position at a point in time.
| 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"]
}
}
CallMcpTool with server, toolName, argumentsCallMcpTool:
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 |
mcps/<server-name>/tools/~/.cursor/mcp.jsonCallMcpToolFor 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:
~/.cursor/mcp.jsonMCP not appearing: