Jentic
Secure access to 1,500+ APIs
About Jentic
Jentic provides a managed connection to more than 1,500 APIs. Its remote MCP server keeps credentials in a central vault and uses just-in-time tooling so assistants fetch only the tools needed for a task, reducing context size and credential exposure.
Connection details
https://api.jentic.com/mcp- Transport
- Streamable HTTP
- Authentication
- OAuth
Setup
claude mcp add jentic --transport http https://api.jentic.com/mcpFrequently asked questions
What is the Jentic remote MCP server?
The Jentic remote MCP server is a hosted Model Context Protocol endpoint at https://api.jentic.com/mcp, so AI assistants can connect to it without installing or running anything locally. Jentic provides a managed connection to more than 1,500 APIs. Its remote MCP server keeps credentials in a central vault and uses just-in-time tooling so assistants fetch only the tools needed for a task, reducing context size and credential exposure.
How do I connect to the Jentic MCP server?
Add the endpoint https://api.jentic.com/mcp to any MCP-compatible client such as Claude Code, Codex, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
Does the Jentic MCP server require authentication?
Yes. Jentic uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.
Which transport does the Jentic MCP server use?
Jentic exposes a Streamable HTTP endpoint, the current standard transport for the Model Context Protocol, supported by all major MCP clients.
More remote MCP servers
.svg){kind=logo}
.svg)
