Documentation Index
Fetch the complete documentation index at: https://veryfront.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
The Veryfront Control Plane exposes MCP tools through JSON-RPC. A client lists tools, selects a tool name, then calls it with JSON arguments.
Use Veryfront Control Plane for the product surface. Use control plane as the shorthand after first mention.
| Tool type | Source | Execution owner | Examples |
|---|
| Platform tools | Built-in Veryfront Cloud capabilities | Veryfront Control Plane | list_projects, list_files |
| Integration tools | Connected integrations and OAuth providers | Veryfront Control Plane, through executeIntegrationTool() | gmail__list_emails, github__list_repos |
| Project tools | Project source, project primitives, or runtime-discovered tools | Project tool runner, reached through control-plane routing | summarize_leads, project tools/* entries |
Client paths
| Client | Tool connection | Project context | Tool coverage |
|---|
| MCP Inspector and external MCP clients | POST /mcp | Bearer token or API key | Platform and integration tools. Project tools are not exposed as one full project catalog on this path. |
| veryfront-agent hosted chat | POST /mcp | Bearer token or API key | Platform and integration tools. Project tools are not exposed as one full project catalog on this path. |
| Project agents | Runtime control-plane stream. Integration tools use /integrations/tools/* | Conversation or agent run project | Runtime project tools, plus integration tools through the control plane. |
| Studio MCP | Studio MCP source | Trusted Studio context headers | Studio and project tools through Studio or project paths. |
| Child and fork runs | Inherited runtime tools and API MCP sources | Parent run project | Runtime, API, and inherited project tools. |
Project context rules
Project context decides which tools appear in tools/list and which project owns a tools/call execution.
| Context source | Used by | Behavior |
|---|
| Bearer token or API key | Public /mcp requests | A project-scoped token selects its project. A user-scoped token uses the environment fallback. |
| Conversation or run project | Project agents and child runs | The run already belongs to a project, so the runtime provides project context. |
| Studio context headers | Studio MCP | Studio passes trusted project context with the request. |
| Project-scoped MCP URL | Target MCP shape | The URL selects the project before tools/list or tools/call. |
project_id inside tool arguments. Select project context at the MCP connection or request layer, then call the tool by name.
tools/list returns tools for the resolved project context.
- Platform tools: Returned when the caller has the required Veryfront permissions.
- Integration tools: Returned when the integration is enabled for the project or connected for the user.
- Project tools: Returned when project source discovery finds them and the MCP path can execute them.
Next
- REST API: Use REST when building backend services and dashboards.
- GraphQL API: Use GraphQL when the client needs typed selection sets.
