Nykst

Model Context Protocol

Use Nykst inside your AI coding agent

Before your agent edits a file, it can ask Nykst what that change will break: which files import it, which pages and API routes it reaches, which tests cover it, and which database tables and services it touches. It takes a few minutes to set up and works with any agent that supports MCP.

1

Map a repository

Nykst can only answer about repositories you have mapped. Connect GitHub, choose a repository and press Start mapping. You choose which repositories Nykst can read, and it never writes to them.

Connect GitHub and map a repo →
2

Create an access token

The token lets your agent read the analysis of your repositories, and nothing else. Nykst stores only a hash of it. You can revoke it here at any time.

Checking your GitHub connection…

3

Add Nykst to your agent

Pick your tool.

Claude Code

One command. Nykst is then available in every project.

The snippets below contain YOUR_NYKST_TOKEN. Create a token in step 2 and they fill in automatically.

  1. Make sure Claude Code is installed: running claude --version in a terminal should print a version.
  2. Run the command below in any terminal (macOS, Linux, Windows PowerShell or Command Prompt).
  3. Start Claude Code and type /mcp. nykst should be listed as connected.
Run in a terminal
Terminal
claude mcp add --transport http --scope user nykst https://nykst-software-intellegence.shuzalniraula.workers.dev/api/mcp --header "Authorization: Bearer YOUR_NYKST_TOKEN"

--scope user makes it available in all your projects. Drop it to add Nykst to the current project only.

File content, not a terminal command
Share with your team: .mcp.json in the repo root
{
  "mcpServers": {
    "nykst": {
      "type": "http",
      "url": "https://nykst-software-intellegence.shuzalniraula.workers.dev/api/mcp",
      "headers": {
        "Authorization": "Bearer ${NYKST_TOKEN}"
      }
    }
  }
}

Commit this file, not your token. Each teammate creates their own token and exports NYKST_TOKEN in their shell.

Check it worked: claude mcp list shows nykst as ✔ Connected, or type /mcp inside a session.

4

Try it

Ask your agent something like this. It decides when to call Nykst, or you can name the tool.

  • get_impact“What breaks if I change src/lib/billing.ts?”

    Files, page and API routes, and tests affected by changing the paths you give it, with exact import lines and recent history.

  • find_usages“Which code reads or writes the users table?”

    Every file and line that touches a database table, an external service, or an environment variable.

  • get_architecture“Give me an overview of this repo's architecture.”

    Overview of the repo: areas, external services, data, most depended-on files, circular imports.

  • search_files“Find the file that exports createCheckoutSession.”

    Find files by path or exported symbol name.

  • list_repositories“Which repositories does Nykst know about?”

    The repositories you have mapped in Nykst.

5

Make your agent check Nykst automatically

Agents call a tool when their instructions say to. Add this to your repository's instruction file so every change starts with an impact check.

Paste into your instruction file
Add to your agent's instruction file
## Nykst (code impact)
Before changing code, use the Nykst MCP tools:
- Call get_impact with the files you plan to edit. Read the direct importers, the affected routes and the tests it lists.
- Call find_usages for any database table, external service or environment variable you touch.
After the change, run the tests Nykst listed and mention anything it flagged in your summary.
  • CLAUDE.md for Claude Code
  • AGENTS.md for Codex, Cursor, Windsurf and others
  • .cursor/rules/nykst.mdc for Cursor
  • .github/copilot-instructions.md for GitHub Copilot

Troubleshooting and safety

Error 401, or “token” in the message
Nykst tells you what is wrong: no token sent, the token is still the placeholder YOUR_NYKST_TOKEN, it doesn't start with nyk_, or it was revoked. Create a new token in step 2 and paste it in place of the placeholder.
“command not found” or the command does nothing
The tool itself isn't installed yet. Check with claude --version, codex --version or gemini --version. On Windows, open a new terminal after installing, and use PowerShell: the export command only exists on macOS and Linux, so use the Windows PowerShell snippet where there is one.
An error in VS Code
Run MCP: List Servers from the command palette, choose nykst, and pick Show Output. It prints the exact reason. Send that text to us if it isn't clear.
“No repository has been analyzed yet”
Map a repository first (step 1). If Nykst says the repository was mapped before code analysis existed, open the graph and press Re-analyze.
The answers look out of date
Nykst answers from the last time you mapped the repository. Press Re-analyze in the graph after you push changes.
What can the token do?
Read the analysis of repositories you mapped: file paths, names of functions and exports, import connections, commit and pull request titles. It cannot read file contents or change anything on GitHub. Revoke it above whenever you want.