API_1_NAME=<name>
(Name of your source API, e.g. “github”)API_1_SWAGGER_URL=<swagger.json-url>
(API Swagger/OpenAPI specification URL, e.g. “https://api.github.com/swagger.json”)API_1_HEADER_AUTHORIZATION=<token>
(API authorization header value, e.g. “github_token”)
Steps
-
Install Meshagent CLI:
-
Sign up & authenticate:
Follow Meshagent CLI setup docs. -
Start the MCP server in a Meshagent Room:
This launches the MCP API Gateway in the cloud, available only in your Meshagent Room. Room/agent shutdown cleans up automatically.
-
Start the chatbot in the same Room:
- This chatbot runs the MCP API Gateway tools. You can add more toolkits if needed.
- When you run this, you’ll get a link to the Meshagent Room.
-
Try it out:
Visit the Room link in your browser. Send messages to the agent to interact with the MCP Server tools.
Project Level Deployment (Persistent Services)
For production, deploy MCP server tools as persistent Meshagent Project Services—your agents and chatbots automatically join every new Room in the project with zero manual steps.-
Create the MCP server project service:
-
Create the Project-level chatbot service:
Tools Available
These tools are provided by the integrated MCP API Gateway server:Tool | Short Description |
---|---|
execute_api | Execute any API endpoint with custom parameters |
get_api_info | Get information about available APIs and endpoints |
Tool Details
execute_api
Execute any API endpoint with custom parameters.
Parameter | Type | Description |
---|---|---|
api_name | string | Name of the API |
method | string | HTTP method (GET, POST, etc.) |
path | string | API endpoint path |
data | object | (optional) Request body data |
headers | object | (optional) Additional headers |
params | object | (optional) Query parameters |
get_api_info
Get information about available APIs and their endpoints.
Parameter | Type | Description |
---|---|---|
api_name | string | (optional) Name of the API (to filter) |