Skip to main content
Glama
Sign In
AgeKey MCP Server

AgeKey MCP Server

by CadamTech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

@agekey/mcp-server

AgeKey MCP Server - Manage AgeKey applications directly from your AI IDE.

Features

  • šŸ” Clerk OAuth Authentication ā€” Seamless login via browser

  • šŸ¢ Multi-Organization Support ā€” Access all your organizations

  • šŸ“± Application Management ā€” Create, list, and manage apps

  • šŸ”‘ Credentials ā€” Get and rotate test/live credentials

  • šŸ”— Redirect URIs ā€” Add and remove callback URLs

  • šŸ›”ļø RBAC ā€” Role-based access control (Member ā†’ test, Admin ā†’ live)

  • šŸ”§ Utilities ā€” JWT decoder, error explainer, code samples

Related MCP server: Gealo MCP Server

Installation

Cursor IDE

Add to your MCP config (.cursor/mcp.json):

{
  "mcpServers": {
    "agekey": {
      "command": "npx",
      "args": ["-y", "@agekey/mcp-server"]
    }
  }
}

Claude Desktop

Add to your config (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "agekey": {
      "command": "npx",
      "args": ["-y", "@agekey/mcp-server"]
    }
  }
}

Authentication

On first use, the MCP server will:

  1. Open your browser to the AgeKey login page

  2. You authenticate with Clerk (existing AgeKey account)

  3. Token is stored locally in ~/.agekey/session.json

No manual token management needed!

The server connects to the production AgeKey Developer Portal by default. Environment configuration (staging, dev, local) is for internal use only and is not documented here.

Available Tools

Organizations

Tool

Description

list_organizations

List all organizations you have access to

Applications

Tool

Description

list_applications

List apps in an organization

get_application

Get app details

create_application

Create a new app (Member+)

Credentials

Tool

Description

get_credentials

Get test or live credentials

rotate_credentials

Rotate credentials (test: Member+, live: Admin+ with confirmation)

Redirect URIs

Tool

Description

add_redirect_uri

Add a callback URI

remove_redirect_uri

Remove a callback URI

Utilities

Tool

Description

decode_jwt

Decode and explain an AgeKey JWT

explain_error

Get help for OIDC error codes

get_code_sample

Get integration code in TypeScript/Python/Go/Java

RBAC Permissions

Role

Test Mode

Live Mode

Viewer

Read only

Read only

Member

Full access

Read only

Admin

Full access

Full access āš ļø

Owner

Full access

Full access āš ļø

āš ļø Live mode operations require explicit confirmation phrases.

Example Usage

You: "List my AgeKey organizations"

Claude: You have access to 2 organizations:
1. Acme Corp (Owner) - 3 applications
2. Side Project (Admin) - 1 application

You: "Create a new app called 'My Game' in Acme Corp"

Claude: āœ… Created application "My Game"

Test Credentials:
- App ID: ak_test_abc123...
- Secret: sk_test_xyz789... āš ļø Save this!

Next steps:
1. Add a redirect URI: http://localhost:3000/callback
2. Try it in the sandbox

You: "Rotate live credentials for My Game"

Claude: āš ļø WARNING: This will rotate LIVE credentials!

To proceed, confirm: "ROTATE LIVE CREDENTIALS"

You: "ROTATE LIVE CREDENTIALS"

Claude: āœ… Live credentials rotated
šŸšØ Update your production environment NOW!

Development

# Install dependencies
pnpm install

# Build
pnpm build

# Run (connects to production portal)
node dist/index.js

License

MIT

Available Tools

11 tools
add_redirect_uriA

Add a redirect URI to an AgeKey application.

For TEST mode: Any valid URL (localhost allowed). Requires Member role. For LIVE mode: Must be HTTPS (no localhost). Requires Admin role AND confirmation.

Inputs: uri (required), appId (required), orgId (required), environment (required), +1 more.

create_applicationA

Create a new AgeKey application. Returns test credentials (secret shown only once!). Requires Admin role or higher in the organization.

Inputs: name (required), orgId (required), description.

decode_jwtA

Decode and explain an AgeKey JWT token. Shows header, payload, expiration status, and human-readable explanation of age verification results.

Inputs: token (required).

explain_errorA

Get a detailed explanation of an AgeKey/OIDC error code including common causes, solutions, and documentation links.

Inputs: errorCode (required), errorDescription.

get_applicationA

Get detailed information about a specific AgeKey application including credentials and redirect URIs.

Inputs: appId (required), orgId (required).

get_code_sampleB

Get integration code samples for AgeKey in various languages. Optionally pre-fill with your app credentials.

Inputs: flow (required), step (required), language (required), appId.

get_credentialsB

Get credentials (App ID, Secret, Authority URL) for an AgeKey application. Specify 'test' or 'live' environment. Requires orgId (the organization that owns the app).

Inputs: appId (required), orgId (required), environment (required).

list_applicationsA

List all applications in an AgeKey organization. Returns app names, IDs, and credential status.

Inputs: orgId (required).

list_organizationsA

List all AgeKey organizations you have access to. Returns organization details including your role and the number of applications.

Inputs: no named parameters.

remove_redirect_uriA

Remove a redirect URI from an AgeKey application.

For TEST mode: Requires Member role. For LIVE mode: Requires Admin role AND confirmation.

āš ļø WARNING: Removing a live URI will immediately break any production integration using it!

Inputs: uri (required), appId (required), orgId (required), environment (required), +1 more.

rotate_credentialsA

Rotate credentials for an AgeKey application.

For TEST mode: Requires Member role or higher. For LIVE mode: Requires Admin role or higher AND explicit confirmation phrase.

āš ļø WARNING: Old credentials are invalidated immediately!

Inputs: appId (required), orgId (required), environment (required), confirmation.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelogā€¦

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.9/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools map cleanly to distinct resources and actions. get_application and get_credentials both surface credential information, which could cause an agent to pick the wrong one, though get_credentials is environment-specific.

    Naming Consistency5/5

    All tools use a consistent snake_case verb_noun pattern (list_*, get_*, create_*, rotate_*, add_*, remove_*), making the set predictable. No mixed conventions or vague verbs.

    Tool Count5/5

    With 11 tools, the set is appropriately scoped for an AgeKey administration and integration server. Each tool addresses a meaningful operation without redundancy or bloat.

    Completeness3/5

    The surface covers org listing, app creation/inspection, credential rotation, redirect URI management, and helpful utilities. However, there is no update or delete application tool, so full application lifecycle management is incomplete.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers