Connect aNewStream to Cursor

Ship code. Update changelog. Same breath.

Published: 2026-02-04

TL;DR

Cursor is an AI coding IDE. Add aNewStream via MCP and your changelog updates as you code. Ship a feature, say "push an update to WIDGET-001 saying added dark mode," keep coding. Link commits to changelog entries. No browser tabs. No context switch. No Alt-Tab dance.

Why Cursor?

You're already talking to AI while you code. You're already describing what you're building in natural language. The only thing missing is a system that listens.

With aNewStream in Cursor:

• Changelog as you code — push updates without leaving the editor
• Commit linking — attach Git URLs to changelog entries for full traceability
• AI-drafted changelogs — GENERATE agent writes release notes from your history
• Context-aware answers — ASK agent knows what you shipped and when

Setup (2 minutes)

Step 1: Create .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "anewstream": {
      "command": "node",
      "args": ["/path/to/aNewStream-01-agents/mcp/index.js"]
    }
  }
}

Step 2: Restart Cursor. The MCP server connects automatically.

Step 3: Verify — say "Test my aNewStream connection" in chat. You should see your org name.

The Workflow

Here's the part that changes everything: you stop switching apps.

1. Ship a feature. Code is committed.

2. Update the changelog. In Cursor chat:

"Push an update to MYAPP-001 saying added dark mode with system preference detection"

3. Link the commit. Optional, but powerful:

"Push an update to MYAPP-001 saying fixed auth bug, commit URL is https://github.com/you/repo/commit/abc123"

4. Generate release notes. End of sprint:

"Generate a changelog entry for MYAPP covering the last 5 updates"

GENERATE agent drafts it. You approve. Done.

Example Session

You: Create a product called TASKFLOW

Cursor: Created product "TASKFLOW"

You: Push an update to TASKFLOW-001 saying initial release with task creation and due dates

Cursor: Update #1 pushed to TASKFLOW-001

You: What's the changelog for TASKFLOW?

Cursor: TASKFLOW-001: initial release with task creation and due dates (Feb 4, 2026)

Three exchanges. Product created, update logged, history queryable. Back to coding.

Per-Project Config

.cursor/mcp.json is per-project. Different projects can use different aNewStream accounts. Share the config with your team for consistent tracking. Add it to .gitignore if it contains API keys.

With API key:

{
  "mcpServers": {
    "anewstream": {
      "command": "node",
      "args": ["./mcp/index.js"],
      "env": {
        "ANEWSTREAM_API_KEY": "ansk_your_key_here"
      }
    }
  }
}

What Maps Where

All 41 tools, 20 resources, 8 AI agents. Same capabilities as every MCP client — just wired into the place where you already live.

Read More

• What is aNewStream? — Start here if you're new
• How Is It Actually Intelligent? — The system that gets smarter over time

Official Docs: Cursor MCP Documentation

Running multiple agents? See how Codex tracks them all →

Other MCP Clients: Claude | ChatGPT | VS Code | Replit | Lovable | Antigravity | Codex

Try It Now → | Back to Home

Contact