Get Started with an agent

You will connect an agent to the Core MCP, then create a target, two credentials, and a proxy through the tools. The agent must already have a user token. Creating that token is on API keys.

Connect to the Core MCP

Add https://api.requestrocket.com/mcp to your agent client as a remote MCP server. Send your user token in the Authorization header. See Authentication with an agent for OAuth and token options.

Read the guide

Call get_guide with guide_key: "proxy-creation". The guide returns the field order and the tools to use. target-creation and credential-creation are also available guide keys.

Find your organisation

Call list_clients. The response includes the clientId you need for every create call below.

Create the target

Call create_target:

clientId — from step 3
targetName — HTTPBin
targetBaseURL — https://httpbin.org
targetRegion — an AWS region, e.g. us-east-2
targetTestPath — /get

Save the targetId from the response.

Create the target credential

Call create_credential:

clientId — from step 3
credentialName — HTTPBin target credential
credentialType — target
credentialAuthType — none
credentialRegion — same region as the target
credentialSecret — {}

Save the credentialId from the response.

Create the inbound credential

Call create_credential:

clientId — from step 3
credentialName — HTTPBin inbound credential
credentialType — proxy
credentialAuthType — key
credentialRegion — same region as the target
credentialSecret — { "key": "Authorization", "value": "my-secret-key", "addToHeader": true }

Save the credentialId from the response.

Create the proxy

Call create_proxy:

clientId — from step 3
proxyName — HTTPBin
proxyRegion — same region as the target
proxyProxyCredentialId — the inbound credential id from step 6
proxyTargetId — the target id from step 4
proxyTargetCredentialId — the target credential id from step 5
proxyActive — true

Save the proxyId from the response.

Get the proxy URL

Call get_proxy_url with the proxyId and proxyRegion from step 7. The response is the regional URL callers use.

Send a test call

Call execute_proxy_read_request with:

proxyUrl — the URL from step 8
path — /get
proxyCredentialToken — my-secret-key

The result has success: true and data.status: 200. data.data is the HTTPBin response.

End-to-end prompt

After the Core MCP is connected, you can give the agent this prompt:

Call get_guide with guide_key set to proxy-creation. In my chosen organisation, create an HTTPBin target at https://httpbin.org with test path /get, a target credential with auth type none, an inbound key credential, and an active proxy. Keep every record in the same region. Show me each created id, get the proxy URL, then call /get through it with the inbound key.

The agent must ask for or infer the organisation and region before it creates the records. Do not put a production secret into the prompt.

Use generate_app_link when a person needs to finish or inspect an action in the app. Pass entity and optional action (create, edit, view, or list). For edit or view, pass entityId. The tool returns a deep link; it does not submit a support request or change the record.

API reference

Use the HTTP API directly

Targets

The upstream API the proxy calls

Proxies

Bind a credential, target, and target credential