Connecting to Jentic Remote MCP Server¶
One MCP server. 1,500+ APIs. No credential risk.
Jentic connects your AI assistant to 1,500+ APIs through a single MCP server. Credentials never touch your prompts — Jentic's managed vault handles auth centrally. Just-In-Time Tooling means agents fetch only the tools they need, keeping context lean and reasoning accurate.
Goal — Connect to the Jentic Remote MCP server using either API Key authentication or OAuth, allowing you to search, load, and execute external APIs directly where you work.
Features¶
- Search & Discover APIs: Search across thousands of available operations and workflows from popular APIs (Gmail, Discord, GitHub, and more) using natural language queries
- Execute Operations & Workflows: Run API operations and multi-step workflows directly from your AI assistant, with automatic credential management and secure execution
- Credential Management: Securely store and manage API credentials for multiple services, with automatic credential selection based on operation requirements
- OAuth 2.0 Authentication: Enterprise-grade OAuth authentication with PKCE support, automatic token refresh, and user consent flows
- Agent-Scoped Access: Operations and credentials are scoped to your agent, ensuring secure access control and isolation
What you'll get¶
With Jentic Remote MCP configured, you'll gain access to powerful tools:
Tools available¶
| Tool available | What it does |
|---|---|
| search_apis | Type what you need (e.g., "Send Discord Message", "Find New York Times Articles") and MCP lists matching APIs. |
| load_execution_info | See the details of any API you found - what information it needs and how to use it. |
| execute | Actually use the API - provide the required information and get results back in the chat. |
Resources available¶
| Resource available | What it does |
|---|---|
| list_credentials | Lists all credentials your agent has access to in .txt format. Can be given to the agent for more context about available integrations. |
Authentication Methods¶
OAuth Connections (Recommended)¶
OAuth is a standard authentication protocol and is recommended for connecting to the Jentic Remote MCP Server. It provides secure, token-based authentication that's managed by the client.
OAuth 2.0 Authentication Requirements: - A valid Jentic account (sign up at jentic.com if you don't have one) - An MCP Configuration set created in your Jentic organization - API credentials configured for the services you want to use (configured through the Jentic dashboard)
The OAuth flow uses PKCE (Proof Key for Code Exchange) for enhanced security and supports automatic token refresh for seamless long-term use.
OAuth Dynamic Client Registration is supported by the following MCP clients:
- Claude Desktop — OAuth authentication
- ChatGPT — OAuth authentication
- Cursor — OAuth authentication (also supports API Key)
- Windsurf — OAuth authentication (also supports API Key)
API Key Connections¶
API Key authentication is supported by the following MCP clients:
- Cursor — API Key authentication (also supports OAuth)
- Windsurf — API Key authentication (also supports OAuth)
Connection Requirements¶
Requires a Jentic account (free) to use tools effectively. For OAuth connections, you'll need an MCP Configuration set created in your Jentic organization. For API Key connections, you'll need a Live Capabilities agent with an associated API key.
Before you start¶
Complete these steps in Jentic before connecting your MCP client:
- Sign in to Jentic — Go to app.jentic.com/sign-in
- Add API credentials — Add any API keys, OAuth tokens, or other credentials you'll need to your registry
Important: Use the same login method (e.g., Google sign in) for both Jentic and your MCP client connection.
Quick start¶
Choose your MCP client and authentication method:
OAuth (Recommended): - Claude Desktop - ChatGPT - Cursor - Windsurf
Note: Additional MCP clients may support connecting to the Jentic Remote MCP Server, but are not currently documented in these guides. If you're using a different MCP client, you can still connect using the same authentication methods (OAuth or API Key) and server URL (
https://api.jentic.com/mcp).
Examples¶
Example 1: Search for articles using NewsAPI¶
User prompt:
Use Jentic to find articles on AI using NewsAPI
What happens: 1. Server searches available operations using search_apis 2. Returns matching actions like "Get top headlines", "Search articles", "Get sources" 3. Provides operation IDs and summaries for each match 4. Uses load_execution_info to load metadata of the selected operation 5. Executes the GET /everything operation with necessary inputs via execute 6. Outputs article results to user
Example 2: Get NVIDIA stock price using Finnhub API¶
User prompt:
Use Jentic to find current price of NVIDIA using Finnhub API
What happens: 1. Server searches for Finnhub operations matching "NVIDIA price" using search_apis 2. Returns matching operations including stock quote endpoints 3. Uses load_execution_info to understand required inputs for the selected operation 4. Executes the stock quote operation with your stored Finnhub credentials via execute 5. Returns real-time NVIDIA stock price data with timestamp
Example 3: Get Bitcoin price using CoinCap API¶
User prompt:
Use Jentic to find current price of bitcoin using coincap API
What happens: 1. Server searches for CoinCap operations matching "bitcoin price" using search_apis 2. Returns matching operations including GET /v3/rates/{slug} for retrieving conversion rates 3. Uses load_execution_info to understand required inputs for the selected operation 4. Executes the GET /v3/rates/bitcoin operation with your stored CoinCap credentials via execute 5. Returns real-time Bitcoin price data with timestamp
Privacy Policy¶
See our privacy policy: https://jentic.com/privacy