OpenAPI SpecからMCPサーバーをたて、OpenAI Agent SDKを使って操作します。
FastMCPはOpenAPI Spec, FastAPI appと統合されており、既存のサーバーを簡単にMCPサーバーとすることができます。
mcp-openapi-proxyなどを用いて、uvx mcp-openapi-proxy
でシンプルに実装できればよかったのですが、微妙に上手くいかずだんねんしました
openapi specはこちらのものを利用しています。
Open API Spec
openapi: 3.0.4
info:
title: Swagger Petstore - OpenAPI 3.0
description: |-
This is a sample Pet Store Server based on the OpenAPI 3.0 specification. You can find out more about
Swagger at [https://swagger.io](https://swagger.io). In the third iteration of the pet store, we've switched to the design first approach!
You can now help us improve the API whether it's by making changes to the definition itself or to the code.
That way, with time, we can improve the API in general, and expose some of the new features in OAS3.
Some useful links:
- [The Pet Store repository](https://github.com/swagger-api/swagger-petstore)
- [The source API definition for the Pet Store](https://github.com/swagger-api/swagger-petstore/blob/master/src/main/resources/openapi.yaml)
termsOfService: https://swagger.io/terms/
contact:
email: apiteam@swagger.io
license:
name: Apache 2.0
url: https://www.apache.org/licenses/LICENSE-2.0.html
version: 1.0.26
externalDocs:
description: Find out more about Swagger
url: https://swagger.io
servers:
- url: /api/v3
tags:
- name: pet
description: Everything about your Pets
externalDocs:
description: Find out more
url: https://swagger.io
- name: store
description: Access to Petstore orders
externalDocs:
description: Find out more about our store
url: https://swagger.io
- name: user
description: Operations about user
paths:
/pet:
put:
tags:
- pet
summary: Update an existing pet.
description: Update an existing pet by Id.
operationId: updatePet
requestBody:
description: Update an existent pet in the store
content:
application/json:
schema:
$ref: "#/components/schemas/Pet"
application/xml:
schema:
$ref: "#/components/schemas/Pet"
application/x-www-form-urlencoded:
schema:
$ref: "#/components/schemas/Pet"
required: true
responses:
"200":
description: Successful operation
content:
application/json:
schema:
$ref: "#/components/schemas/Pet"
application/xml:
schema:
$ref: "#/components/schemas/Pet"
"400":
description: Invalid ID supplied
"404":
description: Pet not found
"422":
description: Validation exception
default:
description: Unexpected error
security:
- petstore_auth:
- write:pets
- read:pets
post:
tags:
- pet
summary: Add a new pet to the store.
description: Add a new pet to the store.
operationId: addPet
requestBody:
description: Create a new pet in the store
content:
application/json:
schema:
$ref: "#/components/schemas/Pet"
application/xml:
schema:
$ref: "#/components/schemas/Pet"
application/x-www-form-urlencoded:
schema:
$ref: "#/components/schemas/Pet"
required: true
responses:
"200":
description: Successful operation
content:
application/json:
schema:
$ref: "#/components/schemas/Pet"
application/xml:
schema:
$ref: "#/components/schemas/Pet"
"400":
description: Invalid input
"422":
description: Validation exception
default:
description: Unexpected error
security:
- petstore_auth:
- write:pets
- read:pets
/pet/findByStatus:
get:
tags:
- pet
summary: Finds Pets by status.
description: Multiple status values can be provided with comma separated strings.
operationId: findPetsByStatus
parameters:
- name: status
in: query
description: Status values that need to be considered for filter
required: false
explode: true
schema:
type: string
default: available
enum:
- available
- pending
- sold
responses:
"200":
description: successful operation
content:
application/json:
schema:
type: array
items:
$ref: "#/components/schemas/Pet"
application/xml:
schema:
type: array
items:
$ref: "#/components/schemas/Pet"
"400":
description: Invalid status value
default:
description: Unexpected error
security:
- petstore_auth:
- write:pets
- read:pets
/pet/findByTags:
get:
tags:
- pet
summary: Finds Pets by tags.
description:
"Multiple tags can be provided with comma separated strings. Use\
\ tag1, tag2, tag3 for testing."
operationId: findPetsByTags
parameters:
- name: tags
in: query
description: Tags to filter by
required: false
explode: true
schema:
type: array
items:
type: string
responses:
"200":
description: successful operation
content:
application/json:
schema:
type: array
items:
$ref: "#/components/schemas/Pet"
application/xml:
schema:
type: array
items:
$ref: "#/components/schemas/Pet"
"400":
description: Invalid tag value
default:
description: Unexpected error
security:
- petstore_auth:
- write:pets
- read:pets
/pet/{petId}:
get:
tags:
- pet
summary: Find pet by ID.
description: Returns a single pet.
operationId: getPetById
parameters:
- name: petId
in: path
description: ID of pet to return
required: true
schema:
type: integer
format: int64
responses:
"200":
description: successful operation
content:
application/json:
schema:
$ref: "#/components/schemas/Pet"
application/xml:
schema:
$ref: "#/components/schemas/Pet"
"400":
description: Invalid ID supplied
"404":
description: Pet not found
default:
description: Unexpected error
security:
- api_key: []
- petstore_auth:
- write:pets
- read:pets
post:
tags:
- pet
summary: Updates a pet in the store with form data.
description: Updates a pet resource based on the form data.
operationId: updatePetWithForm
parameters:
- name: petId
in: path
description: ID of pet that needs to be updated
required: true
schema:
type: integer
format: int64
- name: name
in: query
description: Name of pet that needs to be updated
schema:
type: string
- name: status
in: query
description: Status of pet that needs to be updated
schema:
type: string
responses:
"200":
description: successful operation
content:
application/json:
schema:
$ref: "#/components/schemas/Pet"
application/xml:
schema:
$ref: "#/components/schemas/Pet"
"400":
description: Invalid input
default:
description: Unexpected error
security:
- petstore_auth:
- write:pets
- read:pets
delete:
tags:
- pet
summary: Deletes a pet.
description: Delete a pet.
operationId: deletePet
parameters:
- name: api_key
in: header
description: ""
required: false
schema:
type: string
- name: petId
in: path
required: true
description: Pet id to delete
schema:
type: integer
format: int64
responses:
"200":
description: Pet deleted
"400":
description: Invalid pet value
default:
description: Unexpected error
security:
- petstore_auth:
- write:pets
- read:pets
/pet/{petId}/uploadImage:
post:
tags:
- pet
summary: Uploads an image.
description: Upload image of the pet.
operationId: uploadFile
parameters:
- name: petId
in: path
description: ID of pet to update
required: true
schema:
type: integer
format: int64
- name: additionalMetadata
in: query
description: Additional Metadata
required: false
schema:
type: string
requestBody:
content:
application/octet-stream:
schema:
type: string
format: binary
responses:
"200":
description: successful operation
content:
application/json:
schema:
$ref: "#/components/schemas/ApiResponse"
"400":
description: No file uploaded
"404":
description: Pet not found
default:
description: Unexpected error
security:
- petstore_auth:
- write:pets
- read:pets
/store/inventory:
get:
tags:
- store
summary: Returns pet inventories by status.
description: Returns a map of status codes to quantities.
operationId: getInventory
responses:
"200":
description: successful operation
content:
application/json:
schema:
type: object
additionalProperties:
type: integer
format: int32
default:
description: Unexpected error
security:
- api_key: []
/store/order:
post:
tags:
- store
summary: Place an order for a pet.
description: Place a new order in the store.
operationId: placeOrder
requestBody:
content:
application/json:
schema:
$ref: "#/components/schemas/Order"
application/xml:
schema:
$ref: "#/components/schemas/Order"
application/x-www-form-urlencoded:
schema:
$ref: "#/components/schemas/Order"
responses:
"200":
description: successful operation
content:
application/json:
schema:
$ref: "#/components/schemas/Order"
"400":
description: Invalid input
"422":
description: Validation exception
default:
description: Unexpected error
/store/order/{orderId}:
get:
tags:
- store
summary: Find purchase order by ID.
description:
For valid response try integer IDs with value <= 5 or > 10. Other
values will generate exceptions.
operationId: getOrderById
parameters:
- name: orderId
in: path
description: ID of order that needs to be fetched
required: true
schema:
type: integer
format: int64
responses:
"200":
description: successful operation
content:
application/json:
schema:
$ref: "#/components/schemas/Order"
application/xml:
schema:
$ref: "#/components/schemas/Order"
"400":
description: Invalid ID supplied
"404":
description: Order not found
default:
description: Unexpected error
delete:
tags:
- store
summary: Delete purchase order by identifier.
description:
For valid response try integer IDs with value < 1000. Anything
above 1000 or non-integers will generate API errors.
operationId: deleteOrder
parameters:
- name: orderId
in: path
description: ID of the order that needs to be deleted
required: true
schema:
type: integer
format: int64
responses:
"200":
description: order deleted
"400":
description: Invalid ID supplied
"404":
description: Order not found
default:
description: Unexpected error
/user:
post:
tags:
- user
summary: Create user.
description: This can only be done by the logged in user.
operationId: createUser
requestBody:
description: Created user object
content:
application/json:
schema:
$ref: "#/components/schemas/User"
application/xml:
schema:
$ref: "#/components/schemas/User"
application/x-www-form-urlencoded:
schema:
$ref: "#/components/schemas/User"
responses:
"200":
description: successful operation
content:
application/json:
schema:
$ref: "#/components/schemas/User"
application/xml:
schema:
$ref: "#/components/schemas/User"
default:
description: Unexpected error
/user/createWithList:
post:
tags:
- user
summary: Creates list of users with given input array.
description: Creates list of users with given input array.
operationId: createUsersWithListInput
requestBody:
content:
application/json:
schema:
type: array
items:
$ref: "#/components/schemas/User"
responses:
"200":
description: Successful operation
content:
application/json:
schema:
$ref: "#/components/schemas/User"
application/xml:
schema:
$ref: "#/components/schemas/User"
default:
description: Unexpected error
/user/login:
get:
tags:
- user
summary: Logs user into the system.
description: Log into the system.
operationId: loginUser
parameters:
- name: username
in: query
description: The user name for login
required: false
schema:
type: string
- name: password
in: query
description: The password for login in clear text
required: false
schema:
type: string
responses:
"200":
description: successful operation
headers:
X-Rate-Limit:
description: calls per hour allowed by the user
schema:
type: integer
format: int32
X-Expires-After:
description: date in UTC when token expires
schema:
type: string
format: date-time
content:
application/xml:
schema:
type: string
application/json:
schema:
type: string
"400":
description: Invalid username/password supplied
default:
description: Unexpected error
/user/logout:
get:
tags:
- user
summary: Logs out current logged in user session.
description: Log user out of the system.
operationId: logoutUser
parameters: []
responses:
"200":
description: successful operation
default:
description: Unexpected error
/user/{username}:
get:
tags:
- user
summary: Get user by user name.
description: Get user detail based on username.
operationId: getUserByName
parameters:
- name: username
in: path
description: The name that needs to be fetched. Use user1 for testing
required: true
schema:
type: string
responses:
"200":
description: successful operation
content:
application/json:
schema:
$ref: "#/components/schemas/User"
application/xml:
schema:
$ref: "#/components/schemas/User"
"400":
description: Invalid username supplied
"404":
description: User not found
default:
description: Unexpected error
put:
tags:
- user
summary: Update user resource.
description: This can only be done by the logged in user.
operationId: updateUser
parameters:
- name: username
in: path
description: name that need to be deleted
required: true
schema:
type: string
requestBody:
description: Update an existent user in the store
content:
application/json:
schema:
$ref: "#/components/schemas/User"
application/xml:
schema:
$ref: "#/components/schemas/User"
application/x-www-form-urlencoded:
schema:
$ref: "#/components/schemas/User"
responses:
"200":
description: successful operation
"400":
description: bad request
"404":
description: user not found
default:
description: Unexpected error
delete:
tags:
- user
summary: Delete user resource.
description: This can only be done by the logged in user.
operationId: deleteUser
parameters:
- name: username
in: path
description: The name that needs to be deleted
required: true
schema:
type: string
responses:
"200":
description: User deleted
"400":
description: Invalid username supplied
"404":
description: User not found
default:
description: Unexpected error
components:
schemas:
Order:
type: object
properties:
id:
type: integer
format: int64
example: 10
petId:
type: integer
format: int64
example: 198772
quantity:
type: integer
format: int32
example: 7
shipDate:
type: string
format: date-time
status:
type: string
description: Order Status
example: approved
enum:
- placed
- approved
- delivered
complete:
type: boolean
xml:
name: order
Category:
type: object
properties:
id:
type: integer
format: int64
example: 1
name:
type: string
example: Dogs
xml:
name: category
User:
type: object
properties:
id:
type: integer
format: int64
example: 10
username:
type: string
example: theUser
firstName:
type: string
example: John
lastName:
type: string
example: James
email:
type: string
example: john@email.com
password:
type: string
example: "12345"
phone:
type: string
example: "12345"
userStatus:
type: integer
description: User Status
format: int32
example: 1
xml:
name: user
Tag:
type: object
properties:
id:
type: integer
format: int64
name:
type: string
xml:
name: tag
Pet:
required:
- name
- photoUrls
type: object
properties:
id:
type: integer
format: int64
example: 10
name:
type: string
example: doggie
category:
$ref: "#/components/schemas/Category"
photoUrls:
type: array
xml:
wrapped: true
items:
type: string
xml:
name: photoUrl
tags:
type: array
xml:
wrapped: true
items:
$ref: "#/components/schemas/Tag"
status:
type: string
description: pet status in the store
enum:
- available
- pending
- sold
xml:
name: pet
ApiResponse:
type: object
properties:
code:
type: integer
format: int32
type:
type: string
message:
type: string
xml:
name: "##default"
requestBodies:
Pet:
description: Pet object that needs to be added to the store
content:
application/json:
schema:
$ref: "#/components/schemas/Pet"
application/xml:
schema:
$ref: "#/components/schemas/Pet"
UserArray:
description: List of user object
content:
application/json:
schema:
type: array
items:
$ref: "#/components/schemas/User"
securitySchemes:
petstore_auth:
type: oauth2
flows:
implicit:
authorizationUrl: https://petstore3.swagger.io/oauth/authorize
scopes:
write:pets: modify pets in your account
read:pets: read your pets
api_key:
type: apiKey
name: api_key
in: header
FastMCPのデフォルトの実装ではGET MethodがMCPのResourceとして扱われてしまうらしく、今回は全てのメソッドをToolとして呼び出せるようにしています。
run_mcp_server.py
from typing import Literal
import click
import httpx
import yaml
from fastmcp.server.openapi import (
FastMCPOpenAPI,
RouteMap,
RouteType,
)
api_client = httpx.AsyncClient(base_url='https://petstore3.swagger.io/api/v3')
openapi_spec = yaml.safe_load(open('mcp_demo/openapi.yaml'))
CUSTOM_ROUTE_MAPPINGS = [
# GET requests with path parameters go to ResourceTemplate
# RouteMap(
# methods=['GET'],
# pattern=r'.*\{.*\}.*',
# route_type=RouteType.RESOURCE_TEMPLATE,
# ),
# # GET requests without path parameters go to Resource
# RouteMap(methods=['GET'], pattern=r'.*', route_type=RouteType.RESOURCE),
# # All other HTTP methods go to Tool
RouteMap(
methods=['GET', 'POST', 'PUT', 'PATCH', 'DELETE', 'OPTIONS', 'HEAD'],
pattern=r'.*',
route_type=RouteType.TOOL,
)
]
@click.command()
@click.option(
'--transport',
type=click.Choice(['stdio', 'sse'], case_sensitive=False),
default='stdio',
help='Transport method for the MCP server.',
)
def main(transport: Literal['sse', 'stdio']) -> None:
"""Run the MCP server and use it to process a request."""
mcp = FastMCPOpenAPI(
openapi_spec, client=api_client, route_maps=CUSTOM_ROUTE_MAPPINGS
)
mcp.run(transport=transport)
if __name__ == '__main__':
main()
OpenAI Agent SDKからAPIを操作します。
stdio.py
from agents import Agent, Runner
from agents.mcp import MCPServerStdio
async def main() -> None:
"""Run the MCP server and use it to process a request."""
async with MCPServerStdio(
params={
'command': 'uv',
'args': ['run', 'run_mcp_server.py', '--transport', 'stdio']
}
) as mcp:
agent = Agent(
name='mcp',
model='gpt-4o-mini',
instructions='A simple agent that uses the MCP server to process requests.',
tools=[],
mcp_servers=[mcp],
)
res = await Runner().run(
agent,
'「tag2」のタグを持つペットの名前の先頭に「tag2_」を付けて更新してください。',
)
print(res.raw_responses)
if __name__ == '__main__':
import asyncio
asyncio.run(main())
出力例
[
ModelResponse(
output=[
ResponseFunctionToolCall(
arguments='{"tags":["tag2"]}',
call_id='call_xxx',
name='findPetsByTags',
type='function_call',
id='fc_12345xyz',
status='completed',
)
],
usage=Usage(
requests=1, input_tokens=2816, output_tokens=19, total_tokens=2835
),
response_id='resp_xxx',
),
ModelResponse(
output=[
ResponseFunctionToolCall(
arguments='{"id":5,"name":"tag2_Dog 2","status":"sold","photoUrls":["url1","url2"]}',
call_id='call_xxx',
name='updatePet',
type='function_call',
id='fc_12345xyz',
status='completed',
),
ResponseFunctionToolCall(
arguments='{"id":8,"name":"tag2_Lion 2","status":"available","photoUrls":["url1","url2"]}',
call_id='call_xxx',
name='updatePet',
type='function_call',
id='fc_12345xyz',
status='completed',
),
],
usage=Usage(
requests=1, input_tokens=0, output_tokens=0, total_tokens=0
),
response_id='resp_xxx',
),
ModelResponse(
output=[
ResponseOutputMessage(
id='xxx',
content=[
ResponseOutputText(
annotations=[],
text='「tag2」のタグを持つペットの名前を更新しました。\n\n1. **Dog 2** → **tag2_Dog 2** (状態: sold)\n2. **Lion 2** → **tag2_Lion 2** (状態: available)\n\n両方のペットが正常に更新されました。',
type='output_text',
)
],
role='assistant',
status='completed',
type='message',
)
],
usage=Usage(
requests=1, input_tokens=3378, output_tokens=73, total_tokens=3451
),
response_id='resp_12345xyz',
),
]
入力文 :「tag2」のタグを持つペットの名前の先頭に「tag2_」を付けて更新してください
に対して、適切にLLMがAPIを呼び出せていることが分かります。
ResponseFunctionToolCall(
arguments='{"tags":["tag2"]}',
call_id='call_xxx',
name='findPetsByTags',
type='function_call',
id='fc_12345xyz',
status='completed',
)
ResponseFunctionToolCall(
arguments='{"id":5,"name":"tag2_Dog 2","status":"sold","photoUrls":["url1","url2"]}',
call_id='call_xxx',
name='updatePet',
type='function_call',
id='fc_12345xyz',
status='completed',
),
ResponseFunctionToolCall(
arguments='{"id":8,"name":"tag2_Lion 2","status":"available","photoUrls":["url1","url2"]}',
call_id='call_xxx',
name='updatePet',
type='function_call',
id='fc_12345xyz',
status='completed',
)
ローカル以外でMCP(SSE over Http)サーバーを立てている場合、OpenAI Agent SDKでは以下のように接続できます。
async with MCPServerSse(
params={
'url': '<SERVER URL>',
}
) as mcp: