How to Connect an LLM to a REST API
A step-by-step guide to making any REST API with an OpenAPI spec available to LLMs using FastMCP.
You’ve built a powerful REST API, and now you want your LLM to be able to use it. Manually writing a wrapper function for every single endpoint is tedious, error-prone, and hard to maintain.
This is where FastMCP shines. If your API has an OpenAPI (or Swagger) specification, FastMCP can automatically convert your entire API into a fully-featured MCP server, making every endpoint available as a secure, typed tool for your AI model.
This guide will walk you through converting a public REST API into an MCP server in just a few lines of code.
Every code block in this tutorial is a complete, runnable example. You can copy and paste it into a file and run it, or paste it directly into a Python REPL like IPython to try it out.
Prerequisites
Make sure you have FastMCP installed. If not, follow the installation guide.
Step 1: Choose a Target API
For this tutorial, we’ll use the JSONPlaceholder API, a free, fake online REST API for testing and prototyping. It’s perfect because it’s simple and has a public OpenAPI specification.
- API Base URL:
https://jsonplaceholder.typicode.com
- OpenAPI Spec URL: We’ll use a community-provided spec for it.
Step 2: Create the MCP Server
Now for the magic. We’ll use FastMCP.from_openapi
. This method takes an httpx.AsyncClient
configured for your API and its OpenAPI specification, and automatically converts every endpoint into a callable MCP Tool
.
Learn more about working with OpenAPI specs in the OpenAPI integration docs.
For this tutorial, we’ll use a simplified OpenAPI spec directly in the code. In a real project, you would typically load the spec from a URL or local file.
Create a file named api_server.py
:
And that’s it! With just a few lines of code, you’ve created an MCP server that exposes the entire JSONPlaceholder API as a collection of tools.
Step 3: Test the Generated Server
Let’s verify that our new MCP server works. We can use the fastmcp.Client
to connect to it and inspect its tools.
Learn more about the FastMCP client in the client docs.
Create a separate file, api_client.py
:
First, run your server:
Then, in another terminal, run the client:
You should see a list of generated tools (get_users
, get_user_by_id
) and the result of calling the get_user_by_id
tool, which fetches data from the live JSONPlaceholder API.
Step 4: Customizing Route Maps
By default, FastMCP converts every API endpoint into an MCP Tool
. This ensures maximum compatibility with contemporary LLM clients, many of which only support the tools
part of the MCP specification.
However, for clients that support the full MCP spec, representing GET
requests as Resources
can be more semantically correct and efficient.
FastMCP allows users to customize this behavior using the concept of “route maps”. A RouteMap
is a mapping of an API route to an MCP type. FastMCP checks each API route against your custom maps in order. If a route matches a map, it’s converted to the specified mcp_type
. Any route that doesn’t match your custom maps will fall back to the default behavior (becoming a Tool
).
Learn more about route maps in the OpenAPI integration docs.
Here’s how you can add custom route maps to turn GET
requests into Resources
and ResourceTemplates
(if they have path parameters):
With this configuration:
GET /users/{id}
becomes aResourceTemplate
.GET /users
becomes aResource
.- Any
POST
,PUT
, etc. endpoints would still becomeTools
by default.