Set up AI Accessin five minutes
Four short steps. Get an API key, paste it into Cursor or Claude Desktop, verify the connection, then check the FAQ if anything is off.
Pick your tool
Click your AI tool to jump to the exact setup steps. All paths use the same scopes - the only difference is how the tool authenticates.
1. Get credentials
Two paths, same scopes. Pick by your tool.
API Key (X-API-Key + X-API-Secret)
For Cursor, Claude Desktop, scripts you write yourself. Self-serve in your panel: open API Documentation → Create API Key. Pick the Standard scope set. The secret is shown once - copy it before closing.
Open API DocumentationOAuth 2.1
For ChatGPT, Zapier, Make.com, n8n, and other no-code platforms that need a Login button instead of an API key. In your panel: open OAuth Apps → Register App. The client_id + client_secret are shown once - copy them before closing.
Open OAuth Apps2. Connect Cursor or Claude Desktop
Open your client config and add the Proginter entry. Native remote MCP works on newer versions; the mcp-remote shim is the fallback for older builds. Restart the client after editing.
Cursor
Edit ~/.cursor/mcp.json (create it if missing).
Native remote (newer Cursor)
{
"mcpServers": {
"proginter": {
"url": "https://proginter.com/mcp",
"headers": {
"X-API-Key": "pk_your_public_key",
"X-API-Secret": "sk_your_secret_key"
}
}
}
}Stdio shim fallback (older Cursor)
{
"mcpServers": {
"proginter": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://proginter.com/mcp",
"--header",
"X-API-Key:pk_your_public_key",
"--header",
"X-API-Secret:sk_your_secret_key"
]
}
}
}Claude Desktop
Edit claude_desktop_config.json - the path varies by OS, see the Claude Desktop docs.
Native remote (newer Claude Desktop)
{
"mcpServers": {
"proginter": {
"url": "https://proginter.com/mcp",
"headers": {
"X-API-Key": "pk_your_public_key",
"X-API-Secret": "sk_your_secret_key"
}
}
}
}Stdio shim fallback (older Claude Desktop)
{
"mcpServers": {
"proginter": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://proginter.com/mcp",
"--header",
"X-API-Key:pk_your_public_key",
"--header",
"X-API-Secret:sk_your_secret_key"
]
}
}
}3. Verify your setup
Restart your AI client and ask a read-only question. If it answers with your real account data, you are done.
Ask the AI
"Show me my Proginter account profile."
Expect
A clean response with your name and email - that is a 200 OK from the account_profile tool. If you see a 401, jump to the FAQ below.
4. Connect ChatGPT
ChatGPT Custom GPT Actions need a single Authorization header, so they use OAuth instead of an API key. Register the GPT yourself in your panel, then paste the credentials into the GPT builder.
a. Register an OAuth app
In your panel, open OAuth Apps → Register App. Set the redirect URL ChatGPT will give you (typically https://chat.openai.com/aip/...) and the scopes you need (e.g. websites:files, servers:plan). On save you get a client_id and client_secret - the secret is shown once.
b. Configure the Custom GPT Action
In the GPT builder, choose Authentication: OAuth. Paste:
- Client ID: the client_id you copied from OAuth Apps
- Client Secret: the client_secret you copied at registration (one-time)
- Authorization URL:
https://proginter.com/client/oauth/authorize - Token URL:
https://proginter.com/oauth/token - Scope: space-separated list of the scopes you allowed when registering
- Token Exchange Method:
POST request (default)
For the OpenAPI schema upload, use https://proginter.com/api/v1/openapi.json.
c. Verify
Save the GPT, click "Test", and ask: "Show me my Proginter account profile." ChatGPT will redirect you to a Proginter consent screen the first time. Approve it, then ChatGPT receives a token and answers with your real data.
5. FAQ
Short answers to the things that usually go wrong.
Should I use OAuth or X-API-Key?
Both flows hit the same endpoints with the same scopes - pick by your tool. X-API-Key: best for Cursor, Claude Desktop, and scripts you write yourself - anywhere you control both ends. OAuth: required by ChatGPT Custom GPT Actions and most no-code platforms (Zapier, Make.com, n8n) because they only accept a single Authorization header. You can keep using X-API-Key forever if it works for you - we are not deprecating it.
I get a 401 - what now?
Your credentials are wrong, expired, or a header is missing. X-API-Key path: check both X-API-Key and X-API-Secret are set. If it still fails, rotate the key from the API Documentation page. OAuth path: the access token may have expired (1h TTL) - your tool should auto-refresh. If it does not, the user may need to re-consent.
How do I revoke OAuth access I previously granted?
Open Connected Apps in your client panel sidebar. It lists every OAuth grant - app name, scopes, granted-at, last-used. Click Disconnect to revoke every issued access token + refresh token immediately. The app must be re-authorized to regain access.
A CDN or proxy is between me and Proginter - what then?
Some edges strip custom X-* headers. Two fixes: (a) allow X-API-Key and X-API-Secret to pass through your CDN, or (b) use the stdio shim above - the shim sends headers from your local machine so no edge can strip them. The OAuth Bearer header is standard so most CDNs leave it alone.
How do I see what my client is actually sending?
Hit the diagnostic endpoint with your headers - it echoes back what we received with secrets redacted: https://proginter.com/mcp-diagnostic/echo-headers
What does "destructive confirmation" mean?
Anything that deletes, charges, or replaces data needs explicit approval. Most clients will pop up a confirmation. If yours does not, the AI must include _confirm: true in its tool call. Read-only actions never need it.
All connected?
Generate a key in the panel, paste it into your client config, and ask for your account profile to verify.
