Connect an MCP client

Connect with OAuth or an API key and choose compact or individual tools.

Connect a client that supports remote MCP over HTTP to:

https://mcp.kinesis.network/mcp

Setting	Value
Name	kinesis
Transport	Remote HTTP / Streamable HTTP
Authentication	OAuth, or an API key in the Authorization header
Default catalog	mode=compact — separate read and write tools per resource group

Authenticate

OAuth

1. Add the server URL to your client's remote MCP connections.

2. Start authorization. The client discovers Kinesis authorization metadata from the server's challenge.

3. Sign in, review the requested permissions and choose all or selected organizations on the consent page.

4. Return to the client and refresh its tools.

The client handles refresh-token rotation. Repeating offline_access in a refresh request is accepted and does not add resource permissions. See OAuth for client developers.

API key

1. Create a key in Account settings → API keys.

2. Configure this header using your client's secret or environment-variable mechanism:

Authorization: Bearer kn_your_api_key

1. Refresh the tool list.

Choose scopes, organization or project restrictions, and expiry to match the integration. apps:read and monitoring:read allow permitted app and log reads; add projects:read when listing projects.

Choose a catalog mode

Compact is the default. Without filters, it exposes 18 tools. Reads and changes are separated so clients can distinguish inspection from mutation.

Resource group	Read tool	Write tool
Account	account	account_write
Projects	projects	projects_write
Apps	apps	apps_write
Sharing	sharing	sharing_write
Grids	grids	grids_write
Servers	servers	servers_write
Catalog	catalog	None
Billing	billing	billing_write

These tools run named actions with {action, params}. The three remaining tools are browse_github, read_docs and describe_action.

To check your identity, call tool account with:

{"action": "whoami", "params": {}}

To get an action's complete argument schema, call describe_action:

{"action": "create_app"}

It returns action, tool, title, description, inputSchema and annotations. For create_app, tool is apps_write; for get_app_status, it is apps. Use it before constructing complex inputs such as create_app or update_app. It describes actions in the selected folded groups and is present only when at least one such group is loaded. It does not execute the action.

For a client or integration that calls individual action names, connect with:

https://mcp.kinesis.network/mcp?mode=all

This exposes 93 tools, including whoami and create_app directly. Pass their arguments without an action/params wrapper. browse_github and read_docs are direct calls in both modes; describe_action is a compact-mode helper.

Both modes enforce the same action schemas and permissions. Compact descriptions omit pagination and idempotency fields from short signatures; those arguments remain supported. Some advertised schemas shorten nested configuration, and compact direct-tool schemas omit validation-only constraints. describe_action and the reference provide complete schemas; calls still enforce the full validation rules.

Load selected groups

https://mcp.kinesis.network/mcp?groups=account,projects,apps

For inspection without write actions:

https://mcp.kinesis.network/mcp?groups=account,projects,apps&readonly=true

Group	Includes
account	Identity, organizations, settings, audit, received organization invitations and notifications
projects	Project listing, creation, name/visibility updates and deletion
apps	Apps, templates, placement, moves, lifecycle, logs, usage, builds and domains
github	Connected accounts and repository browsing, including file contents
sharing	Members, roles, ownership, organization invitations, grantees and existing resource invitations
grids	Grid composition, server priority and grid app controls
servers	Orders, server details/logs, BYOD tokens, power, Smart Lifecycle and SSH keys
catalog	Provider catalog and marketplace
billing	Balance, costs, invoices, ledger, payment methods, vouchers and node protection
docs	Built-in guides; always included

No filter loads all groups. groups accepts comma-separated values and repeated query parameters. readonly=true or readonly=1 removes write actions before groups are folded. An unknown group or mode returns 400 invalid_request.

Filters control discovery; scopes and resource access are enforced independently. account must be included explicitly when using a group filter that needs identity or notifications.

Choose the organization

Call account with {"action":"list_orgs","params":{}}. For organization-level actions, put the returned slug inside params.org, for example {"action":"list_members","params":{"org":"acme"}} on sharing. Resource-ID actions resolve the organization themselves. list_projects and list_apps span organizations unless org filters them.

A role, credential scope and organization/project restriction must all permit the action. org_required lists slugs when a call needs one. Connections approved before members:read, members:write, org:write and audit:read existed need re-approval for those permissions.

Verify the connection

1. In compact mode call account with {"action":"whoami"}. In all mode call whoami with {}.

2. Call read_docs with {"topic":"getting_started"}.

3. With projects:read, call projects with {"action":"list_projects","params":{}}, or list_projects in all mode.

If an action fails with insufficient_scope, inspect requiredScopes. Changing the catalog mode or group filter does not grant permission.

Built-in resources

The server advertises nine Markdown resources. Clients without a resource UI can call read_docs with the final path segment as topic.

Resource	Topic
kinesis://docs/getting_started	First deployment
kinesis://docs/deploy	Sources and app configuration
kinesis://docs/operate	Lifecycle, logs, builds and domains
kinesis://docs/troubleshoot	Status and failure diagnosis
kinesis://docs/servers	Grids, dedicated servers and orders
kinesis://docs/billing	Credits, costs and payments
kinesis://docs/organizations	Organizations, members, roles, settings and audit
kinesis://docs/sharing	Adding organization members to resources and grid access
kinesis://docs/errors	Error codes and recovery

The server is stateless and does not provide change-event subscriptions. Send one JSON-RPC message per HTTP request; batches are not supported.

Troubleshooting

Symptom	Check
401 before tools load	Bearer header, key expiry/revocation or OAuth authorization
An individual name such as create_app is missing	Default compact mode uses apps_write with action: "create_app"; use mode=all for individual names
Missing write actions	Check the _write tool and the readonly filter
An action was sent to the wrong tool	Follow the error’s named tool, or read describe_action(...).tool
add_credits or set_auto_reload is missing	These actions are not available through MCP; billing belongs to organization admins
Missing resource family or identity	groups filter; include account for whoami
403 insufficient_scope	requiredScopes and the user's resource role
invalid_request on a compact call	Read issues under params.*; action-schema failures also include inputSchema
404	Use the MCP host and /mcp path above
A subscription request is refused	Use explicit reads with this stateless server
429 rate_limited	Honor Retry-After and reset headers

Next: Agent workflows and Tool reference.