INDIVIDUAL MCP TOOL
plan_path
Deterministic gap analysis for becoming a role, personalized to a user profile: which requirements are met/missing/unclear, which steps remain, estimated remaining years and cost, with every assumption stated explicitly.
LIVE ENDPOINT
https://www.itseasytobe.com/api/mcp
Connect to this endpoint to inspect the live schema for plan_path and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.com-itseasytobe-roles]
url = "https://www.itseasytobe.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"com-itseasytobe-roles": {
"type": "http",
"url": "https://www.itseasytobe.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: com-itseasytobe-roles
Remote MCP URL: https://www.itseasytobe.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"com-itseasytobe-roles": {
"url": "https://www.itseasytobe.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"com-itseasytobe-roles": {
"type": "http",
"url": "https://www.itseasytobe.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "com-itseasytobe-roles",
"transport": "streamable-http",
"url": "https://www.itseasytobe.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
search_roles— List itseasytobe.com's published role guides ('how to become X'), optionally filtered by a free-text query against title, category, and summary.get_role— Full structured, sourced facts for one role: salary (with source and year), timeline, cost, requirements, step-by-step path, FAQ, outlook, honest 'worth it' verdict, sources, and the content verification record (hash + signature).verify_role— Cryptographic verification record for a role's current content: SHA-256 of the canonical content plus an Ed25519 signature, with step-by-step instructions to independently verify against /.well-known/jwks.json.