Manual setup with a personal key

Create a personal key

1. 01Sign in and open your organization's AI tools.
2. 02Choose Connect an AI tool.
3. 03Choose one or more active projects and name the key.
4. 04Select your AI tool, or choose Detect my tool.
5. 05Choose an expiry: 30 days, 90 days, 1 year, or Never expires.
6. 06Create the key and copy the setup prompt into your AI tool, with the intended repository open.

The setup prompt adapts to your tool and operating system. Copying it does not prove the connection worked. Follow any steps the tool reports.

Add the connection yourself

Open your tool's MCP or external-tools settings and add a server with these values.

Name

Praxis

Transport

Streamable HTTP, sometimes labelled HTTP or remote MCP

Server URL

https://praxis.theorem-labs.com/mcp

Authentication

Paste only the key into a Bearer token field. Or set the header Authorization to Bearer YOUR_KEY, with a space before the key.

• Choose the token or header option, not an OAuth sign-in flow.
• Merge the entry into existing configuration so other servers keep working.
• Save, enable the server and reload its tools. Restart the client if it requires it.
• A tool that only supports local servers needs a local bridge that supports Streamable HTTP and forwards the Authorization header.

Check the key from a terminal

These commands ask for the key without saving it in shell history. They read your account details and download the workflow file. They do not create tickets.

read -rsp 'Praxis key: ' PRAXIS_KEY
printf '\n'
curl --fail --silent --show-error \
  -H "Authorization: Bearer $PRAXIS_KEY" \
  'https://praxis.theorem-labs.com/api/meta'
curl --fail --silent --show-error \
  -H "Authorization: Bearer $PRAXIS_KEY" \
  'https://praxis.theorem-labs.com/skill/praxis.md' -o praxis-workflow.md
unset PRAXIS_KEY

$praxisSecret = Read-Host 'Praxis key' -AsSecureString
$praxisCredential = [Net.NetworkCredential]::new('', $praxisSecret)
$praxisHeaders = @{ Authorization = 'Bearer ' + $praxisCredential.Password }
try {
  Invoke-RestMethod -Uri 'https://praxis.theorem-labs.com/api/meta' -Headers $praxisHeaders
  Invoke-WebRequest -Uri 'https://praxis.theorem-labs.com/skill/praxis.md' -Headers $praxisHeaders -OutFile 'praxis-workflow.md'
} finally {
  Remove-Variable praxisSecret,praxisCredential,praxisHeaders -ErrorAction SilentlyContinue
}

Check that the response names the expected organization and includes your project. This proves the key works. It does not yet prove your AI tool is configured.

Add the project workflow

1. 01Read praxis-workflow.md. It contains instructions, not your key.
2. 02Add or reference it using your tool's project-instructions feature. Keep existing repository instructions.
3. 03Record the organization and project key in the repository's non-secret setup notes.

The same file is at https://praxis.theorem-labs.com/skill/praxis.md and needs the same Authorization header. The Claude Code plugin installs the skills for you. See Skills for what each one does.

Verify the connection

1. 01Reload the client's MCP tools and look for praxis_meta. Some clients prefix tool names with the server name.
2. 02Run praxis_meta. Confirm the organization, project and permissions.
3. 03Use board or search_issues to list existing work.

No test ticket is needed.

Edit, regenerate or revoke a key

• Edit key renames it, changes projects or permissions, or adjusts expiry. The key itself stays the same.
• Setup prompt copies the prompt again without changing the key. On a new device you can paste your saved key; it stays in your browser.
• Regenerate key replaces a lost key. Only the owner can do this. Update every tool that used the old key. Access stays the same.
• Revoke a key when its tool no longer needs access.