Connect / Cursor

Verelyn for Cursor

Cursor documents a route for adding a remote server. Verelyn has not tested it, and Verelyn is not listed in a Cursor catalog.

Keep the news that touches your stack one question away, without leaving the editor.

Give this to your assistant
Read Verelyn's setup guide and tell me which route applies to this client: https://verelyn.com/llms.txt
MCP endpoint: https://verelyn.com/api/mcp
An assistant must not invent priorities, complete payment, or activate the service. The person gives explicit approval in the browser.

You approve the sign-in and permissions yourself, in the browser. An assistant never pays or activates Verelyn for you.

Your stack's news, next to your code.

Cursor reads a server from a small JSON file. Once Verelyn is in it, the agent can pull what changed on the vendors and projects you follow.

  • A changelog you did not have to findAsk about a vendor you depend on and get what moved, dated, with the publisher named.
  • Claims you can openEvery update links the sources behind it, so you can check a detail before you change a dependency.
  • Scoped to what you followVerelyn answers about the companies and topics you chose, not about everything.

How Cursor documents adding a remote server.

  1. Open or create mcp.jsonCursor reads ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside one project.
  2. Add the serverAdd this entry, then save the file and restart Cursor:
    {
      "mcpServers": {
        "verelyn": {
          "url": "https://verelyn.com/api/mcp"
        }
      }
    }
  3. Enable it and sign inOpen Customize, then MCPs, enable the server and follow the OAuth prompt Cursor documents for servers that need it.
  4. Approve and askApprove Verelyn's permissions, then ask the agent what changed on a vendor you track.
  • Cursor says enterprise admins can control which servers people may run, and can approve remote servers by URL. A team policy may block this one.

What Cursor hands back.

A short, sourced answer in the chat panel, with the change dated and the original linked.

Example

A package registry announced a tighter publishing policy for maintainers.

The registry's blog dates the change to next month. A maintainer forum thread says existing tokens keep working until they expire.

Why it matters to you

You follow open-source supply chain news. Rotating your publish tokens before the date avoids a failed release.

  • Registry blog post official, gives the date
  • Maintainer forum thread describes the token transition

Questions about Verelyn for Cursor.

Where does the config go?

In ~/.cursor/mcp.json for all projects, or .cursor/mcp.json for one project, as Cursor documents.

Can my company block this?

Yes. Cursor describes team settings that approve remote servers by URL, so an admin policy can stop a new server.

Does it work without signing in?

No. Verelyn needs your approval, so the OAuth step has to finish in the browser.

Will Cursor interrupt me with news?

No. Cursor asks Verelyn only when you or the agent do.

Use Verelyn in your other assistants too.

Tell Verelyn what to follow.

Start with a short interview. Coverage, delivery and assistant connection are shown separately.

Tell Verelyn what to follow →