mcp-teleport / rules
Cursor rule7 starsChanged 17 months agoApache-2.0Archived repositoryView on GitHub
mcp-debug provides core debugging tools to test and explore the functionality implemented in the aggregated MCP server. This guide focuses on mcp-debugs internal debugging capabilities. mcp-debug exposes these categories of internal tools for debugging the aggregated mcp server end-to-end: list_tools: list all the tools exposed by the aggregated mcp server describe_tool: describe a tool exposed by the aggregated mcp server call_tool: execute a tool exposed by the aggregated mcp server "CallTool not implemented" errors - This means the MCP client…
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,144 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository3 other files it gives its agents.
- .cursor/rules/architecture.mdcCursor rule
- .cursor/rules/cursor_rules.mdcCursor rule
- .cursor/rules/self_improve.mdcCursor rule
The file
We split this mcp-debugging.mdc into the rules it gives an agent
11 rules. About 0 are common, 5 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Start by checking the overall health of the system:
- Distinctive: line 27
Verify that all expected MCP servers are properly registered with the aggregator:
- Distinctive: line 33
If a service shows as unhealthy:
- Very specific: line 34
Check its detailed status: core_service_status
- Distinctive: line 36
Check if its MCP client is attached in the service list
- Very specific: line 50
Check core_service_list to see if the service shows a client
- Very specific: line 54
Check logs in the mcp-teleport TUI (if available)
- Very specific: line 55
Use core_service_status for detailed information
- Very specific: line 59
Use core_workflow_validate to check syntax
- Very specific: line 60
Ensure tool names exist (check with mcp_mcp-debug_list_tools)
- Distinctive: line 61
Verify argument schemas match the tool requirements
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
---
description:
globs:
alwaysApply: true
---
## Debugging mcp-teleport via mcp-debug
mcp-debug provides core debugging tools to test and explore the functionality implemented in the aggregated MCP server. This guide focuses on mcp-debugs internal debugging capabilities.
## Core Debugging Tools
mcp-debug exposes these categories of internal tools for debugging the aggregated mcp server end-to-end:
list_tools: list all the tools exposed by the aggregated mcp server
describe_tool: describe a tool exposed by the aggregated mcp server
call_tool: execute a tool exposed by the aggregated mcp server
## Debugging Workflow
### 1. Verify All Services Are Running
Start by checking the overall health of the system:
```
mcp_mcp-debug_call_tool(name="core_service_list", arguments={})
```
### 2. Check MCP Server Registration
Verify that all expected MCP servers are properly registered with the aggregator:
```
mcp_mcp-debug_call_tool(name="core_mcp_server_list", arguments={})
```
### 5. Troubleshoot Connection Issues
If a service shows as unhealthy:
1. Check its detailed status: `core_service_status`
2. Try restarting it: `core_service_restart`
3. Check if its MCP client is attached in the service list
## Important Notes
- The prefix `x_` is configurable via `EnvctlPrefix` in the aggregator config
- Tool names from individual MCP servers get prefixed to avoid conflicts
- The agent automatically handles tool name resolution and routing
- Service health is continuously monitored and reflected in the status
- Workflows provide a way to test complex multi-step operations
## Common Issues and Solutions
**"CallTool not implemented" errors**
- This means the MCP client is not properly attached to the service
- Check `core_service_list` to see if the service shows a client
- The fix involves ensuring `GetServiceData()` returns the MCP client
**Service shows as unhealthy**
- Check logs in the mcp-teleport TUI (if available)
- Use `core_service_status` for detailed information
- Try `core_service_restart` to recover
**Workflow validation fails**
- Use `core_workflow_validate` to check syntax
- Ensure tool names exist (check with `mcp_mcp-debug_list_tools`)
- Verify argument schemas match the tool requirements
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.