MCP API Connect

MCP API Connect lets an assistant work with REST APIs through a locally installed MCP integration and supplied API documentation.

An API bridge rather than a fixed service

MCP API Connect is designed to work from REST API documentation and credentials supplied for a task. It is useful when an assistant needs an application API that has no dedicated MCP connector. The operations available depend on the documentation and credentials, rather than a universal tool list for every service.

Documented setup

The project publishes the mcp-api-connect package and the mcpapiconnect setup command. Its README documents installing the package globally, running the installer and restarting the client. Review the generated client configuration and installed package before introducing a real API credential.

Start with a read operation

Choose a test API and provide clear documentation for one harmless lookup. Verify the requested method, path, parameters and returned response. Then test an invalid parameter and an error response. A fluent summary from the assistant does not prove that the bridge selected the correct endpoint.

Credentials and scope

Use a credential limited to the API and environment involved in the test. Avoid putting secrets into reusable prompts or source-control files. For a write operation, check the exact payload and target before execution. This is a community MIT-licensed integration maintained in the linked repository, with setup behaviour defined by that project rather than by the API provider.

Project documentation

Repository and setup guide