Smithery MCP. Connect your agent to any service, credentials included.

Smithery handles the messy part of connecting your AI agent to outside services. You don't wanna write boilerplate OAuth code or deal with token expiration every time you build something new. Smithery acts as the centralized control plane, letting your agent find and connect to external MCP servers—whether that's Stripe, GitHub, or some niche database—without you needing to manage credentials manually.

Discovering Services

Need to know what services are out there? You use search_servers to scan the entire registry. You can filter results by a server's name, specific tags, or even keywords in its description field; it’ll spit back everything that matches your criteria. Once you narrow down what you need, you can check the core metadata of any registered service using get_server_details.

This lets you confirm the current status and basic info before you commit to connecting.

Inspecting Capabilities

You gotta know exactly what a server can do before your agent tries it. Smithery gives you three main views: first, use get_server_tools to list every single function—or 'tool'—available on that server. This output includes the necessary input schemas and descriptions so your agent knows precisely which actions it can take; it’s like reading a full API contract for its capabilities.

Second, if you wanna see what data is sitting there waiting to be read, get_server_resources returns all exposed data resources, giving you their names and MIME types. Finally, check out the built-in workflows: get_server_prompts lists reusable prompt templates available on a server, which gives your agent pre-defined ways to structure its requests.

Managing Connections and Credentials

Connecting is where Smithery saves your bacon. Instead of handling complex OAuth handshakes yourself, you use create_connection. This tool handles the entire authentication and session complexity automatically for your application. Once that’s done, it gives you a managed connection to use. Need to audit what's hooked up? Run list_connections to get a full list of every existing connection within a specific namespace.

You can also check the status or review details of any single, established link using get_connection. If that service relationship breaks down or you need to cut ties completely, use delete_connection; this removes the server connection from the registry and revokes access immediately, but remember, this action is final.

Security and Monitoring

For security, don't just hand out your main API key. Use create_service_token to generate a secure, time-limited token that has restricted permissions. This keeps the blast radius small for any frontends or agents you deploy. When things get complex and you need to know if a service is performing right, run get_server_analytics.

This pulls usage metrics and adoption data for a named server, helping you spot trends and figure out where performance issues are kicking off. The whole process means your agent doesn't need specialized knowledge of every vendor’s API; it just needs to ask Smithery where the data or service is located.