obligacje.io

Integration documentation

Connect obligacje.io with MCP

MCP gives AI applications access to selected features of our API. We develop the integration alongside the service; your connected application shows the current tools and their descriptions.

Quickstart

MCP server URL

https://api.obligacje.io/mcp
Transport
Streamable HTTP
Authorization
OAuth — sign-in and consent on obligacje.io

Access is free after sign-in, subject to your account’s current limits.

  1. Add a remote MCP server in your AI application and enter the URL above.
  2. Start the connection. The application opens obligacje.io for you to sign in. An active website session lets you continue without signing in again.
  3. Check the application name, metadata origin, callback address and requested permissions, then approve access.
  4. Return to the application, enable the obligacje.io tools and ask a question. For example: “Find an article explaining floating-rate bond coupons.”

Your application must support remote MCP over Streamable HTTP and OAuth with PKCE S256. It can provide its own public Client ID Metadata Document (CIMD); connections are not restricted to selected providers. Adding the server URL does not grant access — your approval is required.

Application setup

ChatGPT

OAuth sign-in supported

Use the ObligacjeIO plugin when it becomes available in the ChatGPT directory, or add the MCP server manually. The plugin is undergoing publication; manual setup does not depend on publication.

  1. If your account has developer mode, enable it in ChatGPT settings. Add a custom connection in Plugins and enter the MCP URL. Availability depends on your account and workspace policy.
  2. Connect your obligacje.io account and approve the requested permissions on the consent screen.
  3. Enable the ObligacjeIO connection in your conversation. Avoid adding another connection to the same server if you already use the plugin.
Application documentation

Claude in the browser

OAuth sign-in supported; claude.ai connection not yet tested

In claude.ai, use a custom remote MCP connector if this feature is available on your account.

  1. Open Connectors in settings, add a custom connector and enter the MCP URL.
  2. Complete sign-in and consent on obligacje.io.
  3. Enable the connector in your conversation and check the available tools.
Application documentation

Cursor

OAuth configuration with a public client ID

Add the configuration below to .cursor/mcp.json in your project or ~/.cursor/mcp.json. Start the connection in Cursor’s MCP settings and approve access in obligacje.io. Compatibility depends on the OAuth support in your Cursor version; a configuration example is not a test of every application version.

Server configuration example

Use the public CLIENT_ID below. No client secret or manually pasted token is required. This example requests catalog read access.

{
  "mcpServers": {
    "obligacje": {
      "url": "https://api.obligacje.io/mcp",
      "auth": {
        "CLIENT_ID": "https://api.obligacje.io/oauth/clients/cursor.json",
        "scopes": [
          "catalog:read"
        ]
      }
    }
  }
}
Application documentation

Codex

OAuth with CIMD and a local callback

Use the ObligacjeIO plugin when it is available in the directory, or add MCP directly. After adding the server, run codex mcp login obligacje --scopes catalog:read. Sign in and approve access in your browser, then return to Codex.

Server configuration example

Add this section to your Codex configuration or run codex mcp add obligacje --url https://api.obligacje.io/mcp. Then start OAuth sign-in.

[mcp_servers.obligacje]
url = "https://api.obligacje.io/mcp"
Application documentation

Other MCP applications

In a compatible client, add the server URL and start OAuth. CIMD or public-client configuration with HTTPS metadata is required. Support differs by application and version; consult the client’s documentation.

Integrating a custom client

Your MCP client needs Streamable HTTP transport and OAuth support. Use server metadata to discover the authorization configuration.

Authorization discovery
An HTTP 401 response points to Protected Resource Metadata in the WWW-Authenticate header. The client discovers the authorization server there and starts Authorization Code with PKCE S256 and the resource https://api.obligacje.io/mcp.
Application identity
Publish a JSON document at a public HTTPS URL with a non-root path. client_id must exactly equal that URL. Include client_name, redirect_uris, token_endpoint_auth_method: none, grant_types: [authorization_code] and response_types: [code]. Add refresh_token to grant_types if your client refreshes access. Send the document URL as client_id in authorization requests. Dynamic registration (DCR) is unavailable.
Callbacks and permissions
Register exact HTTPS callback URLs. Native clients can use HTTP on localhost, 127.0.0.1 or [::1]; only the port may vary during registration matching. Code exchange must repeat the exact URI from authorization. Wildcards, LAN addresses and custom URI schemes are unsupported. Request only the permissions you need: catalog:read and optionally assistant:turn.
Feature discovery
After authorization, call initialize and tools/list. Tool descriptions and schemas provide the integration’s current capabilities. A regular API token or browser session does not replace an MCP OAuth token.
Protected Resource Metadata

Permissions and disconnecting

catalog:read
Read data and materials exposed through MCP, without access to private conversation history or account settings.
assistant:turn
Ask the obligacje.io assistant questions. Each call creates a private conversation in your account and uses your assistant allowance. Your account must also have assistant access.

Revoke access under Account → Connected applications. Signing out of the website does not disconnect an application. A connection can remain active for up to 30 days after approval; disconnecting also prevents token refresh.

Tool results go to the connected application and are also subject to its data policies. Assistant questions and necessary context go to OpenRouter and the model provider under our privacy policy.

Assistant conversations appear in your account history and follow its deletion, export and up-to-12-month retention rules. Disconnecting does not delete these conversations or copies already received by the external application.

Information is educational and does not constitute investment advice. Check sources, citations and stated data gaps.

Privacy policyTerms of service

Troubleshooting

The application cannot connect

Check the exact MCP URL, CIMD support or configured CLIENT_ID, and OAuth with PKCE S256. invalid_client can mean invalid or unavailable metadata; invalid_request can mean a callback that does not match the document. A DCR-only client needs support for another registration method to connect.

Access expired or sign-in does not return to the application

Restart authorization in the application and check your obligacje.io account on the consent screen. Do not paste tokens or authorization links into chat.

Reads work, but the assistant refuses access

Assistant calls require consent for assistant:turn and assistant access in your account. OAuth consent does not grant permissions your account does not have.

A request limit was reached

Wait as instructed and reduce parallel requests. Additional connections do not increase account limits.

The request takes too long or the result is too large

Narrow your question or reduce the results page size. The client may have its own timeout. Do not automatically retry ask_assistant after an error — check account history first.

Integration support

Contact us for help with setup or to connect your own MCP application.

obligacje-io@agentmail.to

Include the application, its version, the time of the problem and an error code. Do not send passwords, tokens, authorization links or private conversation content.