Question 1

What is MCP‑Builder.ai?

Accepted Answer

MCP‑Builder.ai is a no-code tool that connects your AI application to any API — instantly. Just upload your API documentation (e.g. OpenAPI), and we generate a fully functional MCP‑Server for you in seconds. The platform also supports secure authentication, plus connections to databases, XML files, file systems, and other data sources.

Question 2

What is an MCP‑Server?

Accepted Answer

An MCP‑Server acts as a bridge between your existing IT infrastructure (APIs, databases, files, etc.) and AI-powered applications. It makes your internal tools and data accessible to AI models, so they can interact with them securely and reliably — like giving your AI a 'USB port' to plug into your system.

Question 3

What types of data sources can I connect?

Accepted Answer

You can connect almost anything — including:

- REST and GraphQL APIs
- SQL & NoSQL databases (PostgreSQL, MongoDB, etc.)
- Cloud services like GitHub, Slack, Notion
- XML files, local or cloud file systems
- Internal scripts, logs, CLI tools, and more

Question 4

Which transport protocols are supported?

Accepted Answer

We currently support:
- STDIO
- SSE (Server‑Sent Events)
- HTTP‑Streamable (coming soon)

Learn more about transport layers in the official MCP Transport Specification: https://modelcontextprotocol.io/specification/2025-06-18/basic/transports

Question 5

Can I integrate the MCP‑Server with my OpenAI SDK?

Accepted Answer

Yes — MCP‑Servers work out of the box with OpenAI SDKs that support the Model Context Protocol. You can plug them directly into your agent workflows.

Question 6

What capabilities does MCP‑Builder support?

Accepted Answer

MCP‑Builder currently focuses on tool exposure (API, database, and system integrations). Prompt templates and custom resource handling are coming soon.

See the full feature spec: https://modelcontextprotocol.io/specification/2025-06-18/server

Question 7

What authentication does it support?

Accepted Answer

MCP‑Builder supports OAuth 2.0 and API key authentication out of the box. You can configure these methods directly within your server's settings to control access for users or clients. For advanced use cases, we also support custom auth logic through YAML or programmatic extensions.

Question 8

Can I build an MCP‑Server using frameworks myself?

Accepted Answer

While we definitely recommend using MCP‑Builder.ai to save yourself the hassle 😄, you can also build an MCP server from scratch. Frameworks like FastAPI, Spring Boot, and others already support MCP‑style implementations.

Question 9

Can I cancel at any time?

Accepted Answer

Yes. All plans are monthly, with no lock-in. Cancel anytime directly from your dashboard.

Question 10

Can I export or migrate my MCP‑Server?

Accepted Answer

Yes — you can export your full MCP server configuration to run it on your infrastructure.

Note: MCP‑Builder creates infrastructure and config — not custom source code — so there's no traditional codebase to export.

Question 11

Can I generate an MCP‑Server from an existing OpenAPI specification?

Accepted Answer

Absolutely — that's actually the easiest way to get started. Just drag and drop your OpenAPI file on our site, and we'll take it from there.

About APICHAP

Michael Weißenböck

Dominik Rampelt

Supporters & Accelerators

Media Coverage

Apichap: Linzer Startup bringt AI-basiertes Backend-Development

Apichap: Linzer KI-Startup startet Forschungs-Partnerschaft mit FFG-Förderung

Aus guten Gründen

APICHAP: Die Schnittstellen-Plattform "from Developers, for Developers"

APICHAP – blitzschnell einsatzbereite Schnittstellen dank KI

Edison-Preis für Gründer von KI-Startup Apichap