Skip to main content
The clean /mcp URL lists canonical names by default. Existing clients can request legacy discovery explicitly without changing the tools they invoke or their permissions.

​
Canonical names

Veryfront platform tools use canonical names such as veryfront__list_projects and veryfront__get_file. Integration namespaces such as github__ and gmail__ stay unchanged. Project tools keep their exact names. The MCP tool reference lists every tool under its canonical name. Existing unprefixed platform names remain aliases for the same registered tools, with the same permissions and execution behavior. Existing detail links and saved agent selectors remain valid. An alias does not make a runtime-only helper callable over MCP. Canonical agent-reference discovery uses tool_names: "canonical" on veryfront__list_agent_tool_references. Its platform results include legacy_name to identify the stored selector. Submit the returned name when selecting a new tool so the API can validate its owner before storing the compatible selector. Keep untouched saved selectors unchanged. Ambiguous project and platform identities are rejected instead of silently selecting a different tool.

​
Existing clients

Use https://api.veryfront.com/mcp?tool_names=legacy for clients that expect unprefixed discovery names. ?tool_names=canonical explicitly selects the default canonical mode. Both endpoint modes accept registered canonical and legacy invocation names. A client’s explicit params._meta["veryfront/tool-names"] value of "legacy" or "canonical" overrides the connection URL for that discovery request. Maintained Veryfront Code clients request legacy names to preserve existing tool policies and saved selectors. To restore legacy discovery, select ?tool_names=legacy. Invocation aliases stay available while you roll back clients, and existing saved selectors are preserved.

​
Next