> ## Documentation Index
> Fetch the complete documentation index at: https://docs.budecosystem.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Manage MCP capabilities
Create, generate, manage, and govern MCP Foundry capabilities.
Use these workflows to turn enterprise systems and knowledge into reliable agent capabilities. Each workflow ends by attaching the result to a virtual server and testing it before broader use.
```mermaid theme={null}
flowchart LR
A[Create or connect] --> B[Secure and describe]
B --> C[Attach to virtual server]
C --> D[Test in Playground]
D --> E[Observe and govern]
```
## Generate tools from API definitions
The **MCP Tools Generator** accelerates API onboarding. It accepts OpenAPI specification files or URLs, API documentation, and Postman collections, then produces candidate tool definitions that should be reviewed before publication.
1. Open **MCP Tools Generator**.
2. Choose the source type and provide the file or URL.
3. Start the generation job and follow its status in **Generation Jobs**.
4. Review names, descriptions, endpoints, request schemas, authentication assumptions, and visibility for each generated tool.
5. Test generated tools with non-production credentials.
6. Attach only approved tools to a virtual server.
```mermaid theme={null}
flowchart TD
A[OpenAPI, API docs, or Postman collection] --> B[Ingest and parse]
B --> C[Extract endpoints and schemas]
C --> D[Generate candidate tools]
D --> E[Human review and security validation]
E --> F[Approved virtual server]
```
> **Caution:** Generation is an onboarding aid, not an authorization decision. Check every generated endpoint and credential scope, especially for write or destructive operations.
## Connect and publish MCP servers
Use **MCP Servers** to manage external, self-hosted, or deployable MCP services. Browse the registry for pre-integrated options, or register a server using the connection approach appropriate for the deployment. For command-line servers, MCP Foundry can bridge the server so agents can reach it through a managed network endpoint.
After connecting a server:
1. Verify its health and capability catalog.
2. Review the imported tools, resources, and prompts.
3. Restrict access through teams, visibility, and virtual-server composition.
4. Test a representative call in Playground.
5. Monitor logs and error rates after release.
## Govern access and operations
* Use **Teams** to establish ownership and scoped collaboration.
* Use **API Tokens** for programmatic access; rotate and revoke them according to your security policy.
* Configure **Roots** to constrain filesystem access for server workloads to explicitly permitted directories.
* Use **Logs** to trace activity and investigate failures.
* Use dashboard metrics to identify slow endpoints, error-prone tools, and unusual traffic patterns.
For a complete first composition, continue with [Create your first MCP server](../creating-first-mcp-foundry).