Configure
mcp.json
https://api.veryfront.com/projects/{project_reference}/mcp?tool_names=canonical.
Replace {project_reference} with the project UUID or URL-encoded slug. The endpoint
resolves the project context and checks your access to it.
To try a change on staging first, use https://api.veryfront.org/mcp?tool_names=canonical
with a staging credential.
Tool names
Veryfront platform tools use canonical names such asveryfront__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
Keephttps://api.veryfront.com/mcp for clients that expect unprefixed discovery
names, or select ?tool_names=legacy explicitly. 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, remove the tool_names=canonical option or select
?tool_names=legacy. Invocation aliases stay available while you roll back clients,
and existing saved selectors are preserved.