This page is a product walkthrough only—no workspace is queried here. Sign in to the app to configure repositories, boards, and pipelines.
Create one or more workspaces to scope projects and multi-repo contexts before any automation runs.
Connect GitHub or Bitbucket so James can align implementation with your real source tree.
Sync a board so cards, history, and pipeline evidence stay tied to delivery outcomes.
Choose Azure, OpenAI, Claude, or bring your own—James keeps spend and policy under team control.
Define how agents may touch databases so sensitive systems stay under human-reviewed rules.
Describe a feature on a card and let James orchestrate implementation through the same gates your squad already trusts.
Companies, workspaces, and users live in one place so leads can see throughput, quality, and risk without stitching spreadsheets.
Group workspaces and shared policies so every project inherits the same guardrails.
Invite engineers, control scopes, and keep API keys where security expects them.
Repositories, boards, and governance roll out consistently instead of per-team drift.
See pipeline health and outcomes across active work without losing the Jira thread.
An MCP (Model Context Protocol) lets agents use your systems with structured context—not ad-hoc screen scraping.
James maps external APIs into focused MCPs so agents stay inside engineering boundaries.
Start from curated connectors for common enterprise stacks instead of rebuilding glue code.
Preferences, patterns, and review habits travel with you across repos—less re-explaining, more consistent output.
curl -fsSL https://api.anyjames.ai/api/v1/companion/install.sh | bash -s -- \
--ide cursor \
--scope project \
--project-root "$PWD" \
--server-name james-ai \
--platform cursor \
--target-platform linux-amd64 \
--api-url https://api.anyjames.ai \
--tag v0.1.2 \
--token "$JAMES_API_KEY"