FastServe - Remote MCP Servers from OpenAPI Specs

Which MCP clients are supported?

▼

FastServe is tested and verified with Claude Desktop and Claude.ai Web. It implements the standard MCP protocol (SSE transport, JSON-RPC), so it should work with other MCP-compatible clients like Cline (VS Code) and Zed editor, but we haven't production-tested these yet. If you try FastServe with another MCP client, please let us know how it works!

How are credentials stored?

▼

Credentials are encrypted with AES-256-GCM before storage in Cloudflare KV. They're decrypted in-memory only when making API calls to your target API. Credentials are never logged or exposed in MCP responses. All traffic uses HTTPS. However, this is a shared encryption key (not per-user), so this is suitable for testing and development, not production secrets.

What happens after 24 hours?

▼

Servers and credentials are automatically deleted from storage after 24 hours. This expiration exists because FastServe is currently in the MVP phase—we're focused on validating the product and gathering feedback before building more persistent infrastructure. Once we move beyond MVP, we'll introduce user accounts with persistent servers and configurable TTL. For now, you'll need to reconvert your OpenAPI spec when your server expires.

Are there any usage limits?

▼

Yes. During the beta period:
• Server creation: 10 MCP servers per IP per day (resets midnight UTC)
• Tool calls: 100 calls per server per hour
• Global limit: 10,000 tool calls per day across all servers

Servers automatically expire after 24 hours. These limits protect the service during MVP validation. Need higher limits? Let us know your use case.

What authentication types are supported?

▼

Four types: API Key (header/query/cookie), Bearer Token, Basic Auth (username+password), and OAuth2 access tokens (manual paste only). Full OAuth2 authorization flows with refresh tokens are not yet supported—you need to manually paste access tokens. This is planned for a future release.

Can I use private/internal APIs?

▼

Not directly. FastServe runs on Cloudflare's edge network and can only reach publicly accessible APIs. For internal APIs (localhost, VPN, corporate intranets), we're building a local runtime CLI that will allow you to download config from FastServe and run it locally with network access to internal APIs. This is on the roadmap.

Is my data secure?

▼

FastServe uses AES-256-GCM encryption at rest for credentials. All traffic uses HTTPS. The platform runs on Cloudflare Workers with enterprise-grade security. However, this is a beta product with a shared encryption key. We recommend using it for testing and development only, not production secrets or sensitive data. Always review the security model before trusting any third-party service with credentials.

Does FastServe support OpenAPI 2.0 (Swagger)?

▼

No, only OpenAPI 3.x is supported. If you have an OpenAPI 2.0 (Swagger) spec, you can use the Swagger Converter tool to upgrade it to OpenAPI 3.0 format before pasting into FastServe.

Can I extend server lifetime beyond 24 hours?

▼

Not currently. The 24-hour expiration is in place because FastServe is in the MVP phase. We're validating the product and gathering user feedback before investing in persistent infrastructure. Once we move beyond MVP, we'll introduce user accounts with persistent servers and configurable TTL. For now, you'll need to reconvert when your server expires.

Make APIs conversational

MCP Servers from any OpenAPI spec ⚡ Fully managed.

Everything You Need

Remote MCP Servers

Managed Authentication

Edge Performance

Security First

Tested with Claude

Instant Conversion

How It Works

Input Spec

Add Credentials

Get URL

Use Tools

Connect Any API

Your Company's APIs

Long-Tail Tools

Specialized Platforms

No OpenAPI Spec? No Problem

Frequently Asked Questions