Why Use Adapters?
Zero Boilerplate
Generate hundreds of tools from a single specification without writing code for each endpoint.
Type Safety
Automatic schema validation using Zod ensures type-safe inputs and outputs.
Consistency
All tools follow the same patterns for authentication, error handling, and validation.
Maintainability
Update your spec and regenerate tools automatically — no manual updates needed.
Official Adapters
These adapters are maintained by the FrontMCP team and included in@frontmcp/adapters.
More official adapters are coming soon! GraphQL, gRPC, and database adapters are in development.
Community Adapters
Community adapters are created and maintained by the FrontMCP community. While not officially supported, they extend FrontMCP’s capabilities to new APIs and services.How to Find Community Adapters
1
Search npm
Search for packages tagged with
frontmcp-adapter or mcp-adapter:2
Check GitHub Topics
Browse repositories tagged with
frontmcp-adapter on GitHub.3
Join the Community
Visit the FrontMCP Discussions to discover and share adapters.
Featured Community Adapters
This section is for community-contributed adapters. If you’ve created an adapter, submit a PR to add it here!
Submit Your Adapter
Created an adapter? Share it with the community! Submit a PR to add your adapter to this page.
Adapter Template
Use the official adapter structure as a template for building your own adapters.
Creating Custom Adapters
You can create custom adapters to integrate any API or service with FrontMCP. Adapters are TypeScript classes that implement the adapter interface.Basic Adapter Structure
Adapter Best Practices
1. Security First
1. Security First
- Never expose credentials in tool inputs
- Use
authInfofrom context for authentication - Validate and sanitize all inputs
- Document security risk levels
- Implement proper error handling
2. Type Safety
2. Type Safety
- Generate Zod schemas from specifications - Validate inputs at runtime - Provide TypeScript types for all options - Use strict type checking
3. Performance
3. Performance
- Use lazy loading for specifications - Cache generated tools when possible - Implement connection pooling - Handle rate limiting gracefully
4. Developer Experience
4. Developer Experience
- Provide clear documentation - Include working examples - Support common authentication patterns - Add helpful error messages - Write comprehensive tests
5. Maintainability
5. Maintainability
- Follow the official adapter structure
- Version your adapter properly
- Document breaking changes
- Provide migration guides
- Keep dependencies up to date
Publishing Your Adapter
When publishing a community adapter:- Package Name: Use the pattern
@yourscope/frontmcp-adapter-nameorfrontmcp-adapter-name - Keywords: Include
frontmcp,frontmcp-adapter,mcp,adapter - README: Include installation, usage, examples, and security considerations
- License: Use a permissive license (MIT, Apache 2.0, etc.)
- Tests: Include comprehensive test coverage
- TypeScript: Provide TypeScript types and declarations
package.json
Adapter Comparison
Choose the right adapter for your use case:| Adapter | Best For | Authentication | Type Safety | Complexity |
|---|---|---|---|---|
| OpenAPI | REST APIs with specs | Multi-provider | Auto-generated | Low |
| Custom | Any API/service | Fully customizable | Manual schemas | Medium-High |
Next Steps
OpenAPI Adapter
Learn how to use the OpenAPI adapter
Browse Examples
See adapters in action with real examples
Join Community
Get help and share your adapters

