MCP (Model Context Protocol) lets AI assistants such as Claude, Cursor, VS Code Copilot, Codex, Gemini or Windsurf work with your Okinta data: read contacts, orders and invoices, look at your reports, and create or update data when you allow it. Any app that supports remote MCP servers can connect.
Go to Settings → API and create a key with only the permissions the assistant needs (read-only to start). To try things safely, create a test key (okt_test_…): it only reaches your sandbox.
https://api.okinta.io/mcpPaste the message below into Cursor, Claude, ChatGPT (with MCP), or any assistant that can change MCP settings. When it asks for your key, paste the key from Settings → API (use a placeholder in config files, not the real secret in git).
Connect Okinta as a remote MCP server in this app.
- URL: https://api.okinta.io/mcp
- Transport: HTTP (remote / Streamable HTTP)
- Auth header: Authorization: Bearer YOUR_KEY
Pick the right config for this app (for example ~/.cursor/mcp.json in Cursor) and add the server with that header. I will give you the API key in the next message when you ask.
When you are done, list the Okinta MCP tools to confirm it works.claude mcp add --transport http okinta https://api.okinta.io/mcp \
--header "Authorization: Bearer YOUR_KEY"Add this to claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"okinta": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.okinta.io/mcp", "--header", "Authorization:${OKINTA_AUTH}"],
"env": { "OKINTA_AUTH": "Bearer YOUR_KEY" }
}
}
}Most apps take the server address and an Authorization header in their MCP settings (often mcp.json). Cursor (~/.cursor/mcp.json):
{
"mcpServers": {
"okinta": { "url": "https://api.okinta.io/mcp", "headers": { "Authorization": "Bearer YOUR_KEY" } }
}
}Add this to .vscode/mcp.json or run MCP: Open User Configuration:
{
"servers": {
"okinta": { "type": "http", "url": "https://api.okinta.io/mcp", "headers": { "Authorization": "Bearer YOUR_KEY" } }
}
}Add this to ~/.codeium/windsurf/mcp_config.json (Windsurf calls the address serverUrl):
{
"mcpServers": {
"okinta": { "serverUrl": "https://api.okinta.io/mcp", "headers": { "Authorization": "Bearer YOUR_KEY" } }
}
}Keep the key in an environment variable, then add this to ~/.codex/config.toml:
export OKINTA_API_KEY=YOUR_KEY
[mcp_servers.okinta]
url = "https://api.okinta.io/mcp"
bearer_token_env_var = "OKINTA_API_KEY"Add this to ~/.gemini/settings.json:
{
"mcpServers": {
"okinta": { "httpUrl": "https://api.okinta.io/mcp", "headers": { "Authorization": "Bearer YOUR_KEY" } }
}
}If an app only supports local (stdio) servers, use the mcp-remote bridge:
npx -y mcp-remote https://api.okinta.io/mcp \
--header "Authorization: Bearer YOUR_KEY"list_contacts, get_invoice, create_expense, issue_quote, get_profit_and_loss_report…Connecting in one click, without copying a key (sign in with Okinta), for apps that need OAuth.
The MCP server uses the same keys, permissions and limits as the API: an assistant never reaches more than the key's creator can open in the app. Revoke the key in Settings → API to disconnect it at once.