{% extends "base.html" %} {% block title %}AgenticStore Setup{% endblock %} {% block content %}

Connectors

Configure credentials once — all linked tools will use them automatically.

Loading connectors…

Tools

Select which tools to expose in your MCP client. Deselecting keeps them installed but unlisted.

Loading tools…

Clients

Choose your AI client. We'll write the MCP config automatically.

Loading clients…

Agent Orchestration

Manage persistent memory so AI agents can hand off work across sessions and clients.

Loading…

Checkpoints

Loading checkpoints…

Strategy

Free-form markdown. Agents read this to understand your project goals, constraints, and preferred patterns.

Stored Facts

Loading facts…

Session Log

Loading log…

Troubleshoot

Common issues and fixes.

GitHub

401 Bad Credentials

The GitHub API rejected your token. This usually means the token is expired, has the wrong scopes, or was pasted incorrectly.

1
Use a Classic PAT, not a fine-grained token

Fine-grained PATs require explicit per-repo permission grants and often hit unexpected 401s for org repos. A Classic PAT with repo scope is the most reliable option.

2
Generate a new token with the right scope
  1. Go to github.com/settings/tokens/new
  2. Note: agentic-store-mcp
  3. Expiration: your choice
  4. Scopes: check repo (covers contents, issues, PRs, metadata)
  5. Click Generate token and copy it immediately
3
Save it in the Connectors tab

Go to → GitHub → paste the token → Save → Test Connection. You should see ✓ Authenticated as your-username.

4
Never share your token in chat or logs

PATs have the same access as your GitHub account. If you suspect a token was exposed, revoke it immediately at github.com/settings/tokens.

Docker

Secrets configured in webapp not seen by MCP server

When running in Docker, the webapp and the MCP server run in separate containers. Both must mount the same volume for secrets to be shared.

1
Start services with docker compose
docker compose up -d
2
Configure secrets here in the webapp

Go to and save your tokens.

3
Mount the same volume when running the MCP server

Your client config must include the -v flag. See the tab for the exact snippet.

General

Tool returns "PyGithub not installed" or import error

Dependencies aren't installed yet.

1
Run uv sync in the project directory
uv sync

All dependencies (PyGithub, FastAPI, keyring, etc.) are installed by default — no extras needed.

General

Server disconnected — "No module named 'mcp'"

The MCP server process exited immediately after starting. The log shows ModuleNotFoundError: No module named 'mcp' even though the package is listed in pyproject.toml. This usually means the virtual environment is missing or stale.

1
Re-sync the virtual environment
cd /path/to/agentic-store-mcp
uv sync

This installs mcp, PyGithub, keyring, and all other dependencies into the local .venv.

2
Check for a conflicting VIRTUAL_ENV variable

If another project's venv is active in your shell, uv run may warn "VIRTUAL_ENV does not match the project environment path". Deactivate it first, then retry:

deactivate
uv sync
3
Restart your AI client

After syncing, restart Claude Desktop / Claude Code / Cursor so the MCP server process is relaunched with the updated environment.

{% endblock %}