API, MCP & plugins
Choose a connection method. Check the package format for your app.
Choose what to connect
- API key
- A secret that identifies your account and permissions. Your app sends it with an API or MCP request.
- REST API
- HTTP endpoints for your application. Use curl or an HTTP client to start work and read results.
- MCP server
- A service that lists tools for an AI assistant. The assistant calls a tool with structured input and receives a result.
- Plugin
- An installable package for an app. It can include skills, MCP configuration and other components supported by that app.
LeadsAgent’s API and MCP server use the same task services. A plugin can point to that server and add workflow instructions. Installing a plugin still requires account access.
To connect now, use the MCP guide or REST quickstart. These guides describe direct connections. They do not imply that a LeadsAgent marketplace package is published.
LeadsAgent packages and branding
Published by LeadsAgent Team. These version 1.0.1 packages include the LeadsAgent brand asset and the metadata each format supports. They connect through OAuth. Extract a ZIP for local installation, or upload the OpenAI ZIP through its developer dashboard. Downloading a package does not update an existing connection or publish a directory listing.
Portable plugin with logo, composer icon, listing links and team publisher. Public publisher display also requires the verified organization identity.
For clients expecting .codex-plugin/plugin.json. Current clients can use the portable OpenAI package.
Claude plugin manifest, directory icon and policy links, plus .mcp.json. The Claude chat connector has a separate registration.
Strict plugin manifest and mcp_config.json with serverUrl. Its documented manifest has no logo or publisher fields.
Compatibility extension with gemini-extension.json and httpUrl. Consumer users should choose Antigravity. Gemini Apps use the MCP URL directly.
Cursor manifest with team author, homepage and bundled logo. Public listing requires a dedicated public plugin repository.
Portable Agent Plugins manifest and MCP configuration. A branded VS Code Marketplace extension requires a separate extension package.
For plain MCP connections, merge the file for your installed client into its existing configuration. These downloads use OAuth and contain no account secrets. Keep API keys in the client’s private credential store or supported environment references.
Development ZIPs connect to dev.leadsagent.io; use them for the active development server. Standard ZIPs use this deployment’s configured documentation origin, or leadsagent.io by default. Check that the selected server is deployed before installation. Development configurations and checksums
- Claude configuration
- Cursor configuration
- VS Code / Copilot workspace configuration
- VS Code editor compatibility configuration
- Antigravity configuration
- Gemini CLI enterprise configuration
- OpenCode V1 configuration
- OpenCode V2 configuration
- Codex TOML configuration
- Portable MCP configuration
Gemini Apps accept the MCP URL directly; Google documents no custom logo or publisher manifest. Custom Apps currently require an eligible US personal account, age 18+, English and Keep Activity enabled. n8n uses the MCP Client Tool; a branded community node is a separate npm package.
Brand and registration worksheet · Package index and checksums · 512px LeadsAgent logo
Package requirements by app
For plugin authors. Sources checked on 22 October 2026. Check the linked source before submitting a package.
Before publishing
- Validate the package format for the target app. Include skills only when they add useful workflow instructions.
- Use a stable public HTTPS MCP URL. Keep account keys and provider secrets out of the package.
- Test sign-in, permissions, revocation and tool calls in that app. A successful curl request proves only that HTTP path.
- Provide the listing details, support contact, privacy information and review account required by the marketplace.
OpenAI submission requirements and Claude plugin requirements describe their separate review flows.