Quickstart
Choose MCP for an AI app or the SDK for code you own.
Stacklink has two onboarding paths. Choose the one that matches where your agent runs.
| Path | Choose it when | Credential |
|---|---|---|
| Connect to an AI app — MCP | You use Cursor, VS Code, Claude, Codex, or another remote MCP client | The client completes Stacklink OAuth; no API key or session ID is pasted into the app |
| Add to your code — SDK | You own an agent application built with Vercel AI SDK, OpenAI Agents SDK, or Claude Agent SDK | A project-scoped STACKLINK_API_KEY |
Connect an AI app
Open the Stacklink Overview, choose Connect an app, and select your client. Stacklink gives the client a stable project connector URL. The client then asks you to authenticate and approve access.
Add Stacklink
→ approve the server in the AI app
→ sign in to Stacklink
→ approve the project
→ initialize and tools/list complete
→ Stacklink shows ConnectedThe app configuration contains no Stacklink API key and no runtime session ID. Continue with Connect your agent for the exact Cursor, VS Code, Claude, and Codex behavior.
Add Stacklink to your code
Install the public package for your language:
npm install @stacklink/sdkuv add stacklink-sdkThen choose an agent harness. Stacklink supplies executable tools or MCP configuration; the harness owns the model call, tool loop, and final answer.
TypeScript recipes
Vercel AI SDK, OpenAI Agents SDK, and Claude Agent SDK.
Python recipes
OpenAI Agents SDK and Claude Agent SDK.
The complete examples on those pages are generated from the same five executable files used by Stacklink Overview and release certification. They are not handwritten copies.
Registry pages are delivery systems
npm and PyPI host the downloadable packages. Stacklink Overview and this Fumadocs site remain the onboarding and documentation surfaces; Stacklink does not display registry download badges.
What happens after the first tool call
- Stacklink resolves the authenticated project and session.
- Your harness receives only the tools allowed for that session.
- Connected provider accounts remain server-side.
- Mutating operations continue to follow Stacklink permissions and approval policy.
- Close SDK-created sessions in
finally; MCP installation sessions are managed internally by Stacklink.
Next steps
Connect your agent
Install Stacklink in Cursor, VS Code, Claude, Codex, or another MCP client.
Understand MCP authorization
Read the OAuth, session-binding, revocation, and troubleshooting contract.
Connect a provider account
Authorize Gmail, Slack, Linear, and other provider accounts used by Stacklink tools.