Skip to main content
Live. This area is documented as current, user-reliable behavior.

​
Goal

Configure Claude Desktop to reach the scoped StackShift MCP endpoint.

​
Prerequisites

  • A StackShift backend/dashboard with agent connections enabled.
  • Claude account with custom connector access
  • Reachable HTTPS MCP endpoint for hosted client access

​
Workflow

1
Open Settings > Agent connections and choose Claude Desktop.
2
Add an account remote connector and complete browser consent.
3
Review the browser request, return destination, selected resources, requested actions, policy and expiry before granting access.
4
Return to the client and inspect connection identity and authorized resources. Verify actual operation outcomes separately.

​
Setup from the shared catalog

Add an account remote connector and complete browser consent. Open Settings > Agent connections and expand this client. Use the endpoint and resolved instructions shown by your StackShift instance. The templates below contain placeholders, not a deployed endpoint or credential.
  • Setup methods: hosted connector.
  • This catalog entry does not advertise a local configuration scope. Follow its hosted or manual setup instructions.

​
Fetch StackShift guidance through MCP

The connected agent can call the read-only skill_read tool to fetch SKILL.md, references/external-connections.md and the linked task guides. The server introduces this tool during connection setup. No download, local skill installation or native AI credits are needed to read the guides. The client decides when to call tools; connection alone is not proof that it has read the skill. Try this read-only prompt: Use StackShift’s skill_read tool to fetch SKILL.md and references/external-connections.md. Follow the guidance to inspect my connection identity and list only my authorized resources. Do not change anything. Reconnect your client to refresh discovery after an upgrade. Skill guidance does not change your granted resources, permissions or approval requirements.

​
Optional local skill installation

Download StackShift skill v3.4.5 and its SHA-256 checksum. The package contains SKILL.md and all ten reference guides. Use a supported skill import if your client offers one. Otherwise, use the connected skill_read tool; no local installation is required. The skill guides workflows; MCP supplies tools and your consent supplies permissions. The package contains no credentials and grants no new access. Delete only the installed skill folder to uninstall it. MCP authorization remains separate.

​
Authorization and access

Initial discovery requests read access. To create or change resources, authorize the required actions in the browser consent flow. Complete the client authentication step after adding the server. In Settings > Agent connections, review authorized resources, permitted actions, expiry and last observed use. CLI diagnostics check connectivity; inspect the operation result to confirm a deployment completed.

​
Official client references

Catalog documentation review date: 2026-10-01. Requirements may change; consult the linked client documentation.

​
Expected result

A connection with the explicitly consented access. Setup alone does not prove client authentication, deployment success or database readiness.

​
Common failures

  • Hosted clients cannot reach a loopback-only development endpoint.
  • A configured server may still require client authentication.
  • Read access does not authorize mutations. Never work around a denied action with a broader legacy credential.

Connect your coding agent

Connect an external client, choose its access and inspect its work in StackShift.

Connection access and approvals

Understand selected resources, permitted actions, owner decisions and revocation.

Agent connection API and OAuth

Separate owner governance from scoped execution, handle OAuth challenges and recover recorded operations.