Jentic

Jentic MCP Plugin

Why Use Jentic MCP?

Jentic MCP empowers developers to discover and integrate external APIs and workflows rapidly—without the need to write or maintain any API-specific code. By leveraging the MCP protocol and Jentic’s agentic runtime, developers can:

• Search for APIs and workflows by capability, not by vendor or implementation.
• Instantly generate integration code samples that are agnostic to specific API details.
• Avoid boilerplate and reduce maintenance by relying on standardized, declarative integration.
• Focus on building features, while Jentic MCP handles the complexity of API interaction.

API Tools

The Jentic MCP Plugin provides the following tools:

1. search_apis: Search for APIs in the Jentic directory that match specific functionality needs
2. load_execution_info: Retrieve detailed specifications for APIs and operations from the Jentic directory. This will include auth information you may need to provide in your mcpServers.jentic.env configuration.
3. execute: Execute a specific API or workflow operation.

Getting Started

The recommended method is to run the server directly from the GitHub repository using uvx. You will need to install uv first using:

brew install uv or pip install uv

Agent API Key

Create an agent at https://app.jentic.com/sign-in and copy its API key.

Set the key in your MCP client configuration as shown below.

The location of the configuration file depends on the client you are using and your OS. Some common examples:

• Windsurf: ~/.codeium/windsurf/mcp_config.json
• Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json
• Claude Code: ~/.claude.json
• Cursor: ~/cursor/.mcp.json

For other clients, check your client's documentation for how to add MCP servers.

Note: After saving the configuration file, you may need to restart the client application (Windsurf, Claude Desktop) for the changes to take effect.

MCP Tool Use

Once the MCP server is running, you can easily use the MCP tools in your LLM agent to discover and execute APIs and workflows.

1. search_apis: Search for APIs in the Jentic directory that match specific functionality needs
2. load_execution_info: Retrieve detailed specifications for APIs and operations from the Jentic directory. This will include auth information you may need to provide in your mcpServers.jentic.env configuration.
3. execute: Execute a specific API or workflow operation.

Environment Variables

When you are using an API that requires authentication, the load_execution_info tool will describe the required environment variables. You environment variables via the command line in Windsurf, although in some clients like Claude Desktop, you'll need to add them to your MCP config:

Alternative (Using Local Path for Development):

Use this if you are actively developing the MCP plugin locally. Replace /path/to/your/project/mcp with the absolute path to your project directory.

Optional: Add a JENTIC_API_URL environment variable to your mcp_config.json file to point to a specific Jentic API (works with both methods):

Once configured, restart Windsurf, and the Jentic MCP tools will be available.

You can tail the logs generated by the locally running MCP server by running:

Installation

Installing via Smithery

To install Jentic Plugin for Claude Desktop automatically via Smithery:

Manual Installation

Ensure you have pdm installed (pipx install pdm).

To install the package and its dependencies for development:

Running the MCP Server

The Jentic MCP plugin is designed to be run using uvx, which handles environment setup and execution.

Default Mode (Stdio)

Run the MCP plugin directly using uvx, specifying the project directory as the source using --from and the mcp script:

From Local Path (Development):

From Remote Repository (Recommended for general use):

This automatically uses the default serve --transport stdio command defined in the mcp script's callback.

HTTP Modes

The MCP server supports two HTTP transport modes:

• Standard HTTP: Traditional request-response HTTP mode
• Streamable HTTP: HTTP mode with streaming support, compatible with MCP Inspector

Standard HTTP Mode

To run the server in standard HTTP mode (e.g., for testing with claude-cli):

From Local Path (Development):

From Remote Repository (Recommended):

Streamable HTTP Mode

To run the server in streamable HTTP mode (compatible with MCP Inspector):

From Local Path (Development):

From Remote Repository (Recommended):

Running from a Remote Git Repository

You can also run the MCP server directly from a Git repository URL without cloning it locally using uvx --from:

This command fetches the specified version, installs its dependencies in a temporary environment, and runs the default command (which is serve --transport stdio).

You can add other arguments like --log-level DEBUG or --mock after the URL fragment:

To run in HTTP mode from a remote source:

To run in streamable HTTP mode from a remote source:

Other Options

Logging

Mock Mode

Enable mock mode for development without connecting to the actual Jentic API Knowledge Hub:

Environment Variables

Provide environment variables using a .env file:

Using with Claude

The MCP plugin can be used with Claude or other LLMs that support the MCP specification:

Run from Remote Repository (Recommended):

Run from Local Path (Development):

Development

See CLAUDE.md for detailed development instructions.

Package Structure

• src/mcp/: Main MCP package
  • mock/: Mock data providers for development
  • tools.py: Tool definitions
  • handlers.py: Request handlers
  • main.py: CLI entry points
  • adapters/: Adapter implementations
  • core/: Core functionality
• tests/: Test suite

Testing

Linting & Formatting

Uses ruff, black, isort, mypy via pdm scripts.