OpenAPI REST MCP Server
Provides integration with Jira, allowing the MCP server to interact with Jira REST APIs using the configured credentials.
Provides integration with Salesforce, enabling interaction with Salesforce REST APIs using OAuth client credentials.
Provides integration with Zoho CRM, enabling interaction with Zoho CRM REST APIs using OAuth refresh token authentication.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@OpenAPI REST MCP Server Create a new Jira issue in the PROJ project with title 'Fix login bug'."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
OpenAPI REST MCP Server
This MCP server allows Claude Desktop to interact with REST APIs described by an OpenAPI/Swagger specification.
Supported integrations include:
Jira
Zoho CRM
Salesforce
Microsoft SharePoint
Procore
HxGN EAM
Oracle Primavera P6
Authentication methods vary by integration.
Jira, Zoho CRM, Salesforce, SharePoint, and Procore were configured and tested during development.
HxGN EAM and Primavera P6 use Basic Authentication and require credentials from the system administrator before they can be tested.
Requirements
Node.js 18+
Claude Desktop
API credentials for the target system
Setup
Move to directory.
cd openapi-rest-mcpInstall dependencies.
npm installConfiguration
Copy
config.example.jsonto
config.jsonEdit the values as required.
Example:
{
"activeEnvironment": "jira"
}Supported environments
jira
zoho
salesforce
sharepoint
procore
eam
primavera
Claude Desktop Configuration
Add the MCP server to your Claude Desktop configuration.
Example:
{
"mcpServers": {
"openapi-rest": {
"command": "node",
"args": [
"/path/to/src/index.js",
"--config",
"/path/to/config.json"
],
"env": {
"API_USER":"",
"API_TOKEN":"",
"ZOHO_CLIENT_ID":"",
"ZOHO_CLIENT_SECRET":"",
"ZOHO_REFRESH_TOKEN":"",
"SALESFORCE_CLIENT_ID":"",
"SALESFORCE_CLIENT_SECRET":"",
"SALESFORCE_TOKEN_URL":"https://your-instance.my.salesforce.com/services/oauth2/token",
"CLIENT_ID":"",
"CLIENT_SECRET":"",
"TENANT_ID":"",
"PROCORE_CLIENT_ID":"",
"PROCORE_CLIENT_SECRET":"",
"PROCORE_REFRESH_TOKEN":"",
"PROCORE_TOKEN_URL":"https://login-sandbox.procore.com/oauth/token/",
"CLAUDE_CONFIG_PATH":"/Users/<username>/Library/Application Support/Claude/claude_desktop_config.json",
"MCP_SERVER_NAME":"openapi-rest",
"EAM_USER":"",
"EAM_PASSWORD":"",
"PRIMAVERA_USER":"",
"PRIMAVERA_PASSWORD":""
}
}
}
}Replace all placeholder values with your own credentials.
Authentication
Jira
Basic Authentication
Required
API_USER
API_TOKEN
Related MCP server: MCP REST Server
Zoho CRM
OAuth Refresh Token
Required
ZOHO_CLIENT_ID
ZOHO_CLIENT_SECRET
ZOHO_REFRESH_TOKEN
The server automatically refreshes access tokens.
Salesforce
OAuth Client Credentials
Required
SALESFORCE_CLIENT_ID
SALESFORCE_CLIENT_SECRET
SALESFORCE_TOKEN_URL
The server automatically retrieves access tokens.
SharePoint
Microsoft Graph Client Credentials
Required
CLIENT_ID
CLIENT_SECRET
TENANT_ID
The server automatically retrieves access tokens.
Procore
OAuth Refresh Token
Required
PROCORE_CLIENT_ID
PROCORE_CLIENT_SECRET
PROCORE_REFRESH_TOKEN
The server automatically refreshes access tokens.
The latest refresh token is automatically written back to the Claude Desktop configuration file.
HxGN EAM
Basic Authentication
Required
EAM_USER
EAM_PASSWORD
Credentials must be provided by the HxGN EAM administrator.
Primavera
Basic Authentication
Required
PRIMAVERA_USER
PRIMAVERA_PASSWORD
Credentials must be provided by the Primavera administrator.
Running
Start Claude Desktop.
The MCP server will start automatically.
No additional commands are required.
Notes
OAuth access tokens are refreshed automatically where supported.
Procore refresh tokens are automatically persisted.
The active environment is selected in
config.json.
Attribution
This project is based on openapi-rest-mcp by Samet Birer.
The project has been modified and extended as part of an internship project, including additional integrations, authentication workflows, token refresh handling, and configuration support.
Available Tools
12 toolsapi_deleteC
DELETE request to an API endpoint
Inputs: url (required), data, params, headers, +3 more.
api_getC
GET request to an API endpoint
Inputs: url (required), params, headers, maxChars, +2 more.
api_patchB
PATCH request to an API endpoint
Inputs: url (required), data (required), params, headers, +3 more.
api_postC
POST request to an API endpoint
Inputs: url (required), data (required), params, headers, +3 more.
api_putC
PUT request to an API endpoint
Inputs: url (required), data (required), params, headers, +3 more.
config_initA
Write a starter config.json (from config.example.json) so the user can fill it in. Writes to the resolved config path by default; will not overwrite unless force is true.
Inputs: path, force, maxChars.
config_statusA
Report where the config is looked for, whether it was found/loaded, the active environment, and the available environments. Use this to diagnose setup issues.
Inputs: maxChars.
inspect_loginA
POST credentials to the login endpoint and return the raw response plus suggested token paths. Use this to discover the right auth.tokenPath (and verify auto-discovered loginUrl) without committing config.
Inputs: loginUrl, maxChars, credentials, environment.
swagger_fetchC
Fetch and summarize Swagger/OpenAPI documentation for an environment
Inputs: maxChars, environment.
swagger_get_endpointC
Get detailed information about a specific endpoint from Swagger
Inputs: path (required), method (required), maxChars, environment, +1 more.
swagger_get_schemaC
Get a schema/model definition from Swagger documentation
Inputs: schemaName (required), maxChars, environment, resolveRefs.
swagger_list_endpointsB
List API endpoints from Swagger. Optionally fuzzy-search by keyword and/or filter by tag and method.
Inputs: tag, limit, method, search, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Tools are mostly distinct: HTTP methods are separate, Swagger exploration tools have clear purposes (summary vs list vs detail vs schema). Minor ambiguity exists between swagger_fetch (summarize docs) and swagger_list_endpoints (list endpoints), but descriptions resolve it.
Most tools follow a resource_action pattern (api_get, swagger_fetch, config_status). inspect_login breaks the pattern by putting the verb first, but the overall convention is still readable and predictable.
12 tools is well within the ideal range for a REST/OpenAPI server, with no redundancy. Each tool serves a distinct need from documentation exploration to HTTP requests and configuration.
The tool surface covers the full workflow: fetching OpenAPI docs, discovering endpoints and schemas, performing all standard HTTP methods, handling login/token discovery, and managing configuration. No obvious dead ends.
Maintenance
Related MCP Connectors
Connect assistants to your workspace knowledge, skills, and work tools.
Connect ChatGPT or Claude to your CRM, store or shipping API. Keys stay out of the chat.
Create contacts, move deals, send proposals and invoices, read your inbox, from Claude or ChatGPT.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Related MCP Servers
- AlicenseAqualityDmaintenanceA service that dynamically generates MCP tools from Swagger/OpenAPI documentation, allowing Claude Desktop to directly invoke REST APIs through natural language.5MIT
- AlicenseAqualityCmaintenanceEnables interaction with any REST API through token or login authentication, with automatic Swagger/OpenAPI documentation integration for endpoint discovery and comprehensive HTTP request support.7MIT
- AlicenseNot gradedqualityDmaintenanceDynamically generates MCP tools from OpenAPI specifications, enabling AI assistants to interact with any REST API through natural language. Supports multiple APIs with authentication, parameter validation, and integration with Claude Desktop and LangChain.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude Desktop and other MCP clients to interact with any OAuth2-authenticated OpenAPI-based API through automatic tool generation from OpenAPI specifications, with built-in token management and authentication handling.7 npm3MIT