Back to Inline

MCP Documentation

Inline is both an MCP gateway and a configuration tool. The /mcp endpoint proxies tool calls to connected apps, scoped by JWT permissions you configure here.

MCP Gateway Endpoint

Connect MCP clients to this URL. The inline proxies calls to whichever tools the JWT authorises.

—

Add this URL as a custom connector to your AI agent, authenticate and get access to the tools.

Configuration REST API 6

Use these endpoints to manage API configurations and connect apps programmatically.

API Configurations

GET/api/user-apislist_configurations

returns[{api_name, spec, selected_endpoints[], all_available_endpoints[]}]

List all saved API configurations for the authenticated user, including their selected endpoint subsets.

POST/api/fetch-specfetch_spec

body{ url: string }

returns{ api_name, endpoints[], all_available_endpoints[], spec }

Fetch an OpenAPI spec from a URL (or /mcp endpoint). Parses and returns the available tool list ready for configuration.

POST/api/parse-specparse_spec

bodymultipart/form-data — file (YAML or JSON OpenAPI spec)

returns{ endpoints[], all_available_endpoints[], spec }

Upload and parse an OpenAPI 3.x spec file. Alternative to fetch-spec when the spec isn't publicly accessible.

POST/api/save-configsave_config

body{ api_name, spec, selected_endpoints[], all_available_endpoints[] }

returns{ success, api_name, operation_count, message }

Save an API configuration with a chosen subset of endpoints. The saved config is used as the base for token generation.

Single sign-on

POST/api/mint-sso-tokenmint_sso_token

body{ app_url: string }

returns{ sso_token, app_url }

Mint a short-lived SSO token for a connected app. Used by the unified hub to sign users into embedded apps automatically.