Sign Up & Onboarding

Create Your Account

Go to app.runcontext.dev

Click Sign Up. You can create an account with:
- Email + password
- GitHub OAuth (recommended — links to your repos automatically)
Create an organization

After signing up, you’ll be prompted to create an organization. This is your team’s namespace:
- Name: my-company (used in API URLs and the --org flag)
- Display name: “My Company Analytics” (shown in the dashboard)
You can create multiple organizations later (e.g. one per department or client).
Choose a plan
- Free: Skip this step. You can use the CLI locally without a cloud plan.
- Team ($49/mo): Enter payment details. Includes 5 seats and 3 database connectors.
- Enterprise ($299/mo): Contact us or self-serve. Includes unlimited everything.
You can start with Team and upgrade anytime. All plans include a 14-day free trial.
Get your API key

Go to Settings → API Keys in the dashboard. Click Generate Key. Copy the key — you’ll use it to publish and connect your tools.

Store your API key securely. It grants publish and read access to your organization’s semantic planes. You can revoke and regenerate keys anytime.

You need a semantic plane built locally first. If you haven’t done that yet, start with the Quick Start.

Set your credentials
Terminal window
```
export RUNCONTEXT_TOKEN=<your-api-key>
```
Or pass it inline with --token.
Publish
Terminal window
```
context publish --org my-company
```
This compiles your local semantic plane and uploads it to RunContext Cloud. The output shows:
- How many data products were published
- The MCP endpoint URL for your organization
- The dashboard URL to view your published plane
Verify in the dashboard

Go to app.runcontext.dev. You should see your published data products with their tier scores. Browse models, fields, and governance metadata.

Invite team members

In the dashboard, go to Team → Invite. Enter email addresses. Each person gets an invitation to join your organization.

Roles:
- Admin — full access, can manage billing and team members
- Editor — can publish and update semantic planes
- Viewer — read-only access to the dashboard and MCP endpoint
Share the MCP config

Send your team this MCP configuration to add to their AI tools:
```
{
  "mcpServers": {
    "contextkit-cloud": {
      "url": "https://api.runcontext.dev/mcp/my-company",
      "headers": {
        "Authorization": "Bearer <their-api-key>"
      }
    }
  }
}
```
Each team member uses their own API key (generated in their dashboard profile). This works with Claude Code, Cursor, VS Code, Windsurf, and any MCP-compatible tool.
Everyone gets the same context

Once connected, every team member’s AI agent has access to the same semantic planes. When someone publishes an update, all connected tools get the latest version automatically.

Instead of introspecting databases from your local machine, you can connect them directly to the cloud.

Go to Connectors

In the dashboard, click Connectors → Add Connector.
Choose your database

Select from PostgreSQL, MySQL, Snowflake, BigQuery, ClickHouse, Databricks, or SQL Server. Enter the connection details.

For security, connections use SSL/TLS and credentials are encrypted at rest. We recommend creating a read-only database user specifically for ContextKit.
Configure introspection
- Tables to include: Select specific tables or use a glob pattern (e.g. public.*)
- Refresh schedule: How often to re-introspect (daily, weekly, or manual)
- Auto-enrich: Optionally auto-enrich new tables to Silver tier on each refresh
Run the first introspection

Click Introspect Now. The cloud pipeline connects to your database, reads the schema, and creates data products in your organization. View the results in the dashboard.