stellify

Authentication

There are two ways to connect to Stellify: the hosted MCP server with OAuth (recommended — no install, no token), or an API token for the local npm server and direct HTTP requests.

Hosted server with OAuth

Point any MCP-compatible client (Claude Code, Cursor, VS Code Copilot, Claude Desktop) at the hosted server and it will walk you through signing in with your Stellify account in the browser — no token to copy, nothing to install. For example, with Claude Code:

Connect Claude Code to the hosted server

claude mcp add --transport http stellify https://api.stellisoft.com/mcp

The first tool call opens a browser window asking you to sign in and approve the connection; after that, the client holds its own OAuth tokens and refreshes them automatically. The server operates on your active project — the one currently open in Stellify.

API tokens

You should know!

Instructions on how to generate your API token can be found in the Stellify documentation. The token is shown once — store it securely, and please don't commit it to GitHub.

An API token authenticates the hosted server directly (as a bearer token), the local npm server, and plain HTTP requests to the platform API. To run the server locally, add the npm package to your client's MCP configuration:

Local server via npm (mcp.json)

{
  "mcpServers": {
    "stellify": {
      "command": "npx",
      "args": ["-y", "@stellisoft/stellify-mcp"],
      "env": {
        "STELLIFY_API_URL": "https://stellisoft.com/api/v1",
        "STELLIFY_API_TOKEN": "your-api-token-here"
      }
    }
  }
}

The same token works for direct HTTP requests against the platform API:

Example request with a bearer token

curl https://stellisoft.com/api/v1/project \
  -H "Authorization: Bearer {token}"

Always keep your token safe and reset it if you suspect it has been compromised.