Developer Setup Guide

← Back to Documentation

Before you start: Your enterprise admin should have created a grant for you and shared an invite secret (a one-time code). You'll also need the enterprise slug, your member ID, and the project ID for the project you're working on. Check your email — these may have been sent to you.

Install the Corla adapter

Install the adapter globally using npm:

npm install -g @corla/adapter

This gives you the corla CLI command. Verify the installation:

corla status

Log in with your grant

Run the login command with your credentials:

corla login

You'll be prompted for:

Broker URL — https://broker.corla.ai (or the URL your admin provided)
Enterprise slug — e.g. acme-engineering
Member ID — the identifier your admin assigned to you
Project ID — the project you're working on
Invite secret — the one-time code from your admin (first login only)

On success, you'll receive a token. The CLI will show you how to set it:

export CORLA_TOKEN=eyJhbGci...your-token-here

Add this to your shell profile (~/.zshrc or ~/.bashrc) so it persists across terminal sessions.

Keep your token private. Never commit it to git, share it in chat, or include it in screenshots. It grants access to your enterprise's context. If compromised, ask your admin to revoke the grant.

Configure your project

Navigate to your project directory and run:

cd /path/to/your/project
corla init

This creates an .mcp.json file in your project root that configures Corla as an MCP server:

{
  "mcpServers": {
    "corla": {
      "type": "http",
      "url": "https://broker.corla.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${CORLA_TOKEN}"
      }
    }
  }
}

If you use VS Code, it also creates .vscode/mcp.json for VS Code Copilot integration.

Start using enterprise context

That's it. Your AI tools will now automatically load enterprise context when working in this project. The context is fetched from the broker, compiled and scoped to your role, and delivered to your AI tool.

Claude Code

Context loads automatically via MCP

Cursor

Reads .mcp.json for context

VS Code Copilot

Uses .vscode/mcp.json

To verify the connection is working:

corla status

You should see your enterprise name, project, role, and token expiry.

—

What happens under the hood

When your AI tool starts a session, it connects to the Corla broker via MCP and:

Your token is validated and checked against the revocation list
Your grant, role, and project are verified
Relevant assets are compiled — redacted, scoped to your role, and signed
The compiled context is delivered to your AI tool in-memory (never written to disk)
Every access is logged in an immutable audit trail

You never see the raw assets. Your AI tool receives processed context that helps it write better, more aligned code — without exposing the enterprise's proprietary material.

Troubleshooting

"Token expired" or "401 Unauthorized"
Your token has expired. Run corla login again to get a new one. Update CORLA_TOKEN in your shell profile.

"Grant not found" or "Policy denied"
Your grant may have been revoked or expired. Contact your enterprise admin to check your grant status.

"Invalid invite secret"
Invite secrets are single-use. If you've already used it, you don't need it again. If you haven't and it's not working, ask your admin to revoke the grant and create a new one.

MCP server not showing up in your AI tool
Make sure CORLA_TOKEN is set in your environment and .mcp.json exists in your project root. Restart your AI tool after adding the config.

Need help?

If you run into any issues, reach out to your enterprise admin or contact us at info@noitechnologies.com.