MCP Tools DirectoryAbout this integration
Turn any OpenAPI/Swagger spec into an MCP server - every API operation becomes an agent tool.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.1
- Package
- agentify-openapi
- Last compatibility test
- Not independently tested
Connect your agent
agentify-openapiPublisher documentation and package metadata were reviewed offline; neither the package nor a target API was executed. Authentication varies with the selected API and can be bearer, basic, API key, raw headers, or absent, so it is not reduced to a single native mechanism.
Capabilities: Convert OpenAPI and Swagger operations into MCP tools, Filter generated tools by tag, method, or name, Call target APIs with configured headers or credentials
Connected profiles
Additional details
io.github.sani-savaliya/agentify
Source ↗ · Checked 2026-09-170.1.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17agentify-openapi
Source ↗ · Checked 2026-09-190.2.0
Source ↗ · Checked 2026-09-19An MCP client launches the configured npx command for one selected specification; after optional credentials are supplied through environment variables, tool calls do not require a documented interactive authorization step.
Source ↗ · Checked 2026-09-19Target-API authentication is specification-dependent; the publisher documents bearer tokens, HTTP basic credentials, API keys, query keys, and raw headers. Classified unknown because no single native auth value describes all targets.
Source ↗ · Checked 2026-09-19The publisher provides an MCP client configuration that runs npx -y agentify-openapi followed by the specification URL or file.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19