find_endpoint

MCP tool from Slnmap by EMahmoudNabil

route (required: a template or a concrete path), verb (optional)

How to use it

Project documentation lists find_endpoint for the Slnmap MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.

Install Slnmap

$claude mcp add slnmap -- slnmap serve --db C:/path/to/your/project/slnmap.db
FULL SLNMAP LISTING

Other tools in Slnmap (14)

find_circular_dependencies

scope (optional: project/namespace, default project)

find_implementations

fqn (required)

find_orphan_calls

category (optional: no-match/verb-mismatch/verb-unknown)

find_symbol

query (required), kind (optional)

find_tests_for_symbol

fqn (required)

find_usages

fqn (required)

get_architecture_overview

(none)

get_dependencies

fqn (required), direction (optional: outgoing/incoming, default outgoing), depth (optional, 1–3, default 1)

get_project_dependencies

project (optional, default all)

get_symbol_source

fqn (required), contextlines (optional, 0–20, default 5)

get_type_hierarchy

fqn (required), direction (optional: up/down/both, default both), depth (optional, 1–10, default 5)

impact_analysis

fqn (required)

list_endpoints

verb (optional: GET/POST/PUT/DELETE/PATCH), prefix (optional route prefix, e.g. /api/vendors)

list_frontend_callsites

verb (optional), prefix (optional)