Connect Stackportfolio to your coding agent
Stackportfolio is an MCP server. Connect it to Claude Code, Cursor, Codex or any client that speaks Streamable HTTP with OAuth, and manage your profile and projects from the terminal.
MCP server: https://stackportfol.io/mcp
Claude Code
Add the server directly. This gives you the tools without any skills.
- Add the server to your client. In Claude Code:
claude mcp add --transport http stackportfolio https://stackportfol.io/mcp
- Run /mcp, choose stackportfolio and sign in. Your browser opens: approve the scopes on the consent page.
Other clients
Claude.ai and Claude Desktop
Open Settings, then Connectors, choose Add custom connector and paste the server address above.
Cursor
Add this to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for every project, then sign in from Cursor's MCP settings:
{
"mcpServers": {
"stackportfolio": {
"url": "https://stackportfol.io/mcp"
}
}
} Codex CLI
Register the server, then sign in:
codex mcp add stackportfolio --url https://stackportfol.io/mcp codex mcp login stackportfolio
Or add it to ~/.codex/config.toml:
[mcp_servers.stackportfolio] url = "https://stackportfol.io/mcp"
Anything else
Any client that supports Streamable HTTP and OAuth only needs the server address above.
Uploading images
Agents upload screenshots without base64. Ask the agent to call create_project_media_upload with the project, a filename and a content type (PNG, JPEG or WebP). The agent receives a signed upload URL and sends the file with:
curl -T shot.png -H "Content-Type: image/png" "<uploadUrl>"
The URL works once and expires after 10 minutes, so no API key is needed. A used URL is refused with 409, an expired one with 410, a file over the size limit with 413. If an upload fails after the check, ask the agent for a new URL.
Sign-in and access
The client registers itself and asks you to approve scopes. Skills are specific to Claude Code; other clients get the tools only.
Tool calls count against the same rate limits as API requests. Disconnecting the app on your connected apps page ends its access at once.
Manage connected appsTroubleshooting
- A scope error means the client holds fewer permissions than the tool needs: run /mcp and re-authorize.
- If the client never opens a browser, run /mcp and choose stackportfolio, or remove the server and add it again.