Login

u/Impressive-Owl3830

r/Shooting r/sideprojects r/vibecoders_ r/A2AProtocol r/cofoundermatch r/SEO r/mcp r/GithubCopilot r/AMA r/cofounderhunt r/16VCFund r/FlutterDev r/devtools r/MCPservers r/OpenSourceAI r/Startups_EU r/grumpyseoguy r/torvian_eu r/vibecoding r/8080AI r/JulesAgent r/vibecodingcommunity
Image 1 — OpenSource MCP of the week - Chrome DevTools MCP - 53.2k Stars- 100% free
Image 2 — OpenSource MCP of the week - Chrome DevTools MCP - 53.2k Stars- 100% free
▲ 26 r/MCPservers

OpenSource MCP of the week - Chrome DevTools MCP - 53.2k Stars- 100% free

I came across this amazing MCP related GitHub repo - 100% open source and free.

Chrome DevTools for agents (chrome-devtools-mcp) lets coding agents like Claude, Cursor, or Copilot control and inspect a live Chrome browser. It is the official Chrome DevTools MCP server for reliable automation, in-depth debugging, and performance analysis (~52.7k stars on GitHub).

Post link / GitHub repo in comments below.

Features
• control and inspect a live Chrome browser from your coding agent
• record traces and pull actionable performance insights via Chrome DevTools
• advanced debugging: network requests, screenshots, console messages with source-mapped stacks
• reliable automation with Puppeteer, including automatic waits
• slim/headless mode for basic browser tasks
• works with Antigravity, Claude, Cursor, Copilot, and other MCP clients

Install

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": ["-y", "chrome-devtools-mcp@latest"]
    }
  }
}

Requires Node.js LTS, current stable Chrome, and npm. Optional slim mode: add "--slim" and "--headless" to the args array.

u/Impressive-Owl3830 — 5 days ago
▲ 15 r/MCPservers

OpenAI introduced - "MCP Events" let ChatGPT subscribe to updates from your MCP server

OpenAI has just introduced " MCP Events"

It just Implement event subscriptions and webhook delivery for your MCP server.

launch post in comments below.

MCP Events lets ChatGPT subscribe to updates from your MCP server - things like new messages, content updates, or status changes. Users pick what to monitor and what ChatGPT should do when an update lands.

Use cases

• Turn feedback into pull requests - Monitor #product-feedback for bug reports and open draft pull requests with fixes and tests. Event: message.created (filtered by channel_id)

• Apply document feedback - Watch a document for review comments and implement any requested edits. Event: comment.created (filtered by document_id)

Before you start

MCP Events in ChatGPT needs MCP 2.0 (protocol version 2026-07-28). Wire your server into your plugin, keep persistent subscription storage, and allow outbound HTTPS to callback URLs.

ChatGPT supports webhook delivery and callback verification from the draft MCP Events spec. Polling, streaming, and the draft’s gap / terminated control notifications are not supported in this integration.

How it works

  1. Your server lists the events it supports.
  2. The user tells ChatGPT what to monitor and how to respond.
  3. ChatGPT subscribes through your MCP server and supplies a callback URL and signing secret.
  4. Your server sends matching events to that URL.
  5. ChatGPT receives the event in the subscribed chat and follows the user’s instructions.

Advertise event support

Event discovery starts with your server’s capabilities. Add events to the capabilities returned by server/discover:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "resultType": "complete",
    "supportedVersions": ["2026-07-28"],
    "capabilities": {
      "tools": {},
      "events": {}
    }
  }
}

Implement these three event methods on the same authenticated MCP endpoint as your tools:

• events/list - Describe available events and their filters. • events/subscribe - Create or refresh a subscription. • events/unsubscribe — Stop a subscription.

Define an event

An event definition tells ChatGPT what users can subscribe to and which filters are available. Return these from events/list (name, delivery modes, subscription arguments, payload schema).

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "events": [
      {
        "name": "comment.created",
        "description": "A new review comment was added to the specified document.",
        "delivery": ["webhook"],
        "inputSchema": {
          "type": "object",
          "properties": {
            "document_id": {
              "type": "string",
              "description": "ID of the document to monitor for new review comments."
            }
          },
          "required": ["document_id"],
          "additionalProperties": false
        },
        "payloadSchema": {
          "type": "object",
          "properties": {
            "document_id": { "type": "string" },
            "comment_id": { "type": "string" },
            "text": { "type": "string" },
            "url": { "type": "string" }
          },
          "required": ["document_id", "comment_id", "text", "url"],
          "additionalProperties": false
        }
      }
    ]
  }
}

inputSchema is what ChatGPT passes when it subscribes. payloadSchema is the data object on each delivered event.

Use stable event names and specific descriptions. Expose filters (document, project, channel IDs) and apply them on your server before delivery. Only return events the connected account is allowed to see.

Create a subscription

When a user asks to monitor an event, ChatGPT calls events/subscribe with the event name, filter arguments, and webhook destination:

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "events/subscribe",
  "params": {
    "name": "comment.created",
    "arguments": {
      "document_id": "doc_123"
    },
    "delivery": {
      "mode": "webhook",
      "url": "https://receiver.example.com/mcp-events/callback_123",
      "secret": "whsec_<base64-encoded-signing-key>"
    },
    "cursor": null
  }
}

Before accepting the subscription:

  1. Check the user is authorized for that event and arguments.
  2. Validate the event name and arguments against your definition. Require a whsec_ signing secret whose base64 value decodes to 24–64 bytes.
  3. Validate and verify the callback URL.
  4. Store the subscription, owner, filters, callback URL, signing secret, and expiration.

Derive a deterministic subscription ID from the authenticated principal, callback URL, event name, and arguments. Return it with the granted expiration:

{
  "jsonrpc": "2.0",
  "id": 2,
  "result": {
    "id": "sub_123",
    "refreshBefore": "2026-10-02T12:00:00Z",
    "cursor": null,
    "truncated": false
  }
}

Make subscription creation idempotent - update the existing one when identity matches.

Verify the callback

Before sending application data, verify the callback with a signed request and a fresh, single-use, short-lived challenge:

{
  "type": "verification",
  "challenge": "a-single-use-random-value"
}

Sign the body with the subscription secret. Include webhook-id, webhook-timestamp, webhook-signature, and X-MCP-Subscription-Id. ChatGPT echoes the challenge on success. Require 2xx and compare the challenge in constant time before activating delivery.

Require HTTPS. Block private/local addresses. Do not follow redirects.

Send an event

When a matching event fires, POST one event object to the subscription callback:

{
  "eventId": "evt_456",
  "name": "comment.created",
  "timestamp": "2026-10-01T12:05:00Z",
  "data": {
    "document_id": "doc_123",
    "comment_id": "comment_456",
    "text": "Can we add the rollout dates to this section?",
    "url": "https://docs.example.com/doc_123#comment_456"
  },
  "cursor": null
}

Keep a unique eventId across retries. timestamp is ISO 8601 with timezone. name must match the subscription; data must match payloadSchema. Put app fields inside data. Treat user-authored text as data — do not put model instructions in the payload.

Sign the request (Standard Webhooks)

Headers:

• Content-Type: application/json • webhook-id: same as body’s eventId • webhook-timestamp: Unix seconds • webhook-signature: Standard Webhooks HMAC signature • X-MCP-Subscription-Id: id from events/subscribe

Serialize the body once and sign those exact bytes.

Send a signed event with Node.js

npm install standardwebhooks

import { Webhook } from "standardwebhooks";

export async function sendEvent(subscription, event, webhookFetch) {
  const body = JSON.stringify(event);
  if (Buffer.byteLength(body, "utf8") > 256 * 1024) {
    throw new Error("Event payload exceeds 256 KiB");
  }

  const signedAt = new Date();
  const signer = new Webhook(subscription.secret);
  const response = await webhookFetch(subscription.url, {
    method: "POST",
    redirect: "error",
    signal: AbortSignal.timeout(10_000),
    headers: {
      "Content-Type": "application/json",
      "webhook-id": event.eventId,
      "webhook-timestamp": String(Math.floor(signedAt.getTime() / 1000)),
      "webhook-signature": signer.sign(event.eventId, signedAt, body),
      "X-MCP-Subscription-Id": subscription.id,
    },
    body,
  });

  return { accepted: response.ok, status: response.status };
}

Handle delivery responses

A 2xx acknowledges receipt. ChatGPT processes asynchronously.

One event per request. Body max 256 KiB. Retry transient failures with exponential backoff; keep the same eventId and refresh the signature each attempt. Do not retry 410 or 413.

Events can arrive out of order - make write tools idempotent.

Manage subscriptions

Keep subscription state for the lifetime you grant, including across restarts. Recheck access over time and stop delivery if access is revoked.

Refresh: ChatGPT calls events/subscribe again before refreshBefore. Unsubscribe: events/unsubscribe with the original name, arguments, and callback URL — stop delivery and return {}.

Test in ChatGPT

  1. Confirm server/discover and events/list return the expected definitions.
  2. Confirm events show on your plugin page next to tools (rescan after changes).
  3. Start a chat, ask ChatGPT to subscribe, and say what to do when events arrive.
  4. Confirm events/subscribe lands with the right name and arguments.
  5. Confirm callback verification succeeds and the subscription is stored.
  6. Trigger a matching event; confirm the webhook gets 2xx.
  7. Confirm ChatGPT receives the data and responds as instructed.
  8. Trigger a non-matching filtered event and confirm it is not delivered.
  9. Stop monitoring in ChatGPT; confirm events/unsubscribe and delivery stops.
u/Impressive-Owl3830 — 15 days ago
▲ 4 r/OpenSourceAI

OpenSource Repo (900 ⭐️) -mcpc-universal CLI client for MCP-100% free

Playing around with various MCP's this weekend and Came across this an amazing MCP related GitHub repo - 100% open source and free - so sharing.

mcpc is Apify’s universal CLI client for MCP.

Github Repo in comments below

IIt translates every MCP operation into shell commands, letting you debug servers, automate workflows, or give AI agents complete MCP access via a single Bash() call: sessions, OAuth, tools, resources, prompts, tasks, and beyond.

Features

  • Complete MCP coverage: tools, prompts, resources, async tasks, skills, notifications, logging (stdio + Streamable HTTP)
  • Persistent sessions across several servers (stateful or stateless)
  • Progressive tool discovery to cut token usage
  • Code mode: JSON output plays nicely with jq, xargs, and shell pipelines
  • OAuth 2.1 (CIMD + DCR) with credentials stored in the OS keychain
  • MCP proxy for AI sandboxes (keeps tokens out of generated code)
  • Lightweight CLI (Mac/Win/Linux), no LLM needed; experimental x402 payments on Base

Install

With homebrew (macOS /Linux), brings its own Node.js:

brew install apify/tap/mcpc
or ,install the latest node js or Bun first, then:
npm install -g /mcpc
# Or with Bun
bun install -g /mcpc
npm install -g /mcpc

Quickstart

# List all active sessions and saved authentication profiles
mcpc

# Log in to a remote MCP server and save OAuth credentials for future use
mcpc login mcp.apify.com

# Create a persistent session and interact with it
mcpc connect mcp.apify.com 
mcpc               # show server info and capabilities
mcpc  tools-list   # list available tools
mcpc  tools-call search-actors keywords:="website crawler"

# Use JSON mode for scripting
mcpc --json  tools-list

# Use a local MCP server package (stdio) referenced from a config file
mcpc connect ./.vscode/mcp.json:filesystem 
mcpc u/fs tools-list
u/Impressive-Owl3830 — 18 days ago
▲ 4 r/vibecodingcommunity

Top mobile App builder?

Hey all,

What are the top mobile builder apps we have?

I'm trying to build a multiplayer app , for non-tech teammates who have no affinity for code , and just look at the code scares them ( so claude code/codex is out of equation..also desktop app)

The mobile app will be on Flutter.

I shortlist these two tools

Nowa.dev

Flutterflow.io

Both have advantages and disadvantages but I like, for Nowa, the visual ability to write the code, so my teammates can see what is being built

Is also very focused on Flutter so presumably writes quality code

FlutterFlow, on the other hand, has a lot of custom code for Flutter, not from the core library but from their own custom code and I'm not sure if that would be a challenge.

Has anyone had experience building with these two tools? Please share your exp.

reddit.com
u/Impressive-Owl3830 — 25 days ago
▲ 3 r/MCPservers

OpenSource MCP of the week - Nosana MCP - 100% free

I came across this amazing MCP related GitHub repo - 100% open source and free.

Nosana MCP lets your AI agent rent a GPU and deploy models on Nosana. Browse ready-to-run templates (MiniMax H3, Qwen/Gemma LLMs, ComfyUI, Jupyter, VS Code), compare live GPU markets, estimate cost, deploy, and get the running endpoint back — paid with Nosana credits via one API key. No wallet, no tokens. Companion CLI nosana-deploy ships in the same package.

Post link / GitHub repo in comments below.

**Features**

  • MCP tools to list templates/GPUs, recommend a plan, estimate cost, deploy, wait for online, and stop
  • Templates: MiniMax H3 video, Qwen & Gemma LLMs, ComfyUI, Jupyter, VS Code
  • Live GPU markets with ready_now / queued / risk buckets and prices matching the dashboard
  • Guard rails: confirm=true before spending, no silent queueing, no accidental duplicates, real readiness probes
  • Works with Claude Code, Claude Desktop, Cursor, Codex, and other MCP clients
  • Companion CLI nosana-deploy for humans, scripts, and CI (MIT)

Quick start

1. Credits and an API key

Sign in at deploy .nosana .com.

Billing: add credits with a card

Account > API Keys > Create Key. Copy it once.

2. Add the server to your client

Claude Code:

claude mcp add nosana --env NOSANA_API_KEY=nos_your_key -- npx -y nosana-mcp
Claude Desktop, Cursor, Windsurf and most other clients take the same JSON:
{
  "mcpServers": {
    "nosana": {
      "command": "npx",
      "args": ["-y", "nosana-mcp"],
      "env": { "NOSANA_API_KEY": "nos_your_key" }
    }
  }
}

Codex CLI:

codex mcp add nosana --env NOSANA_API_KEY=nos_your_key -- npx -y nosana-mcp

Running from a clone instead of npm:

git clone https://github.com/SohniSwatantra/nosana-mcp.git && cd nosana-mcp
npm install && npm run build
# then point your client at:  node /absolute/path/to/nosana-mcp/dist/mcp/index.js
u/Impressive-Owl3830 — 1 month ago
▲ 2 r/MCPservers

Sampling is deprecated. If your server was borrowing the user's model, you now need your own API key.

The 2026-07-28 spec went final six weeks ago.

Every post/tweet/reddit post I saw covered the same thing:

stateless core, no more Mcp-Session-Id, round-robin load balancing, ship it.

IMO , Nobody covered the deprecations. They're four sentences at the bottom of the release post and they're the part that actually changes what you can build.

  • Sampling (sampling/createMessage)
  • Roots (roots/list)
  • Logging
  • Dynamic Client Registration, in favour of Client ID Metadata Documents
  • Legacy HTTP+SSE transport

All of it keeps working for at least 12 months. No wire-level changes. The deprecation is advisory.

So this is not a fire drill :)

But sampling is different from the other four, and I think the difference got lost.

Why sampling make sense or important atleast

Sampling was the one primitive where your server could use an LLM without owning one.

The server asks the client ---> run an inference using whatever model the user already has configured.

--> No API key on your side. No contract with a provider. No token bill.

so what user's client pays, because the user's client was already paying.

Take that away and every server that wanted to do a little summarizing, classifying, or reranking has to bring its own key + its own provider relationship, & its own margin on tokens.

again i think - That is a different business for anyone shipping a hosted server and it is totally a different weekend project for anyone shipping a free one.

That's the actual change. not "one RPC got a deprecation annotation." rather a cost transfer from client to server operator.

now lets talk about maintainers' case, (trying to) stated fairly

SEP-2577 is not arbitrary and the reasoning is public. The three features were flagged in a core contributor meeting as having the weakest adoption-to-complexity ratio in the spec.

Roots has vague semantics that overlap with tool parameters.

Logging duplicates things you already have.

And sampling, per the SEP, is the most security-sensitive of the three, so removing it is a net positive for security.

The adoption argument is the i agree very strong but client support for sampling was thin atm.

so if you think - A feature almost nobody implemented was imposing a cost on every client and server author who had to read past it in the spec.

dont get me wrong - I don't think that's wrong. although - I think it's the right call for the spec and the wrong outcome for a specific class of server, and both of those can be true at same time.

What I am thinking of doing this month

Ranked by how much it makes a difference and not by written about in posts in general,

1. Audit whether you call sampling/createMessage. If you do, you have 12-15 months to either add a provider key or restructure so the host does the inference and hands you the result.

12 months sounds long. It isn't, if it changes your pricing.

2. Check your transport. Legacy HTTP+SSE is deprecated with a one-year offramp. If you're on it, this is the least interesting migration on the list and the one most likely to bite you silently.

3. DCR to CIMD. Only matters if you're exposing a server on the internet with OAuth. DCR still works for compatibility with authorization servers that don't do CIMD yet. Not urgent, but it's on the clock.

4. Roots and logging. If you're using them, stop adding new usage. Otherwise ignore.

5. Everything about statelessness. Genuinely good, genuinely the headline, genuinely not something most single-instance servers need to act on this week. If you're not running behind a load balancer, this changed nothing about your day.

this is likely - overblown

The stateless migration panic. If your server holds real state, you mint an explicit handle from a tool and pass it back as an argument. The spec's own guidance is that this is better than session state hidden in the transport, because the model can see the handle.

if you point your agents (Astra /fable5.1 of the world) That's a max 40 mins change for most servers, not a rewrite.

The bigger risk iis not migration. It's that the spec is now moving damn fast enough that "I built this in March" means something different century ( in AI times) and there's no good signal in any registry for which spec version a server actually speaks.

Questions I am still puzzled with and need answers for sure.

  1. Is there a good example of a ship sampling in production? The SEP says adoption was low. I'd like to hear from anyone it's breaking, because that's the population the roughly 12- 14 months window is for.
  2. How are you handling inference in your server now? Own key and eat the cost OR push it to the host OR drop the feature entirely?
  3. Should the registry expose spec version? RN you can't tell from a listing whether a server speaks 2026-07-28 or something from last year. Seems like it should be a field ?

BTW - I run r/MCPservers and go through the spec changelogs (whenever my kid stays in school) so the weekly posts here stay current.

If you maintain a server and hit something in this migration that isn't in the docs, post it, that's the stuff worth having here in one place.

reddit.com
u/Impressive-Owl3830 — 1 month ago
▲ 15 r/vibecodingcommunity

Share you project - get featured in this week's community newsletter

Latest edition of vibecodingnewsletter.com is due to out this weekend.

share your interesting vibecoded projects and it will be get featured in new "Community Highlights" section.

subscribe to read last edition of newsletter which feature Grokbot , instinct and others.

reddit.com
u/Impressive-Owl3830 — 1 month ago
▲ 56 r/MCPservers

OpenSource Repo of week - Apify mcpc - universal CLI client for MCP - 100% free

I tried this week an amazing MCP related GitHub repo - 100% open source and free.

mcpc is Apify’s universal CLI client for MCP.

GitHub repo - https://github.com/apify/mcpc

It maps every MCP operation to shell commands so you can debug servers, script workflows, or give AI agents full MCP access through a single Bash() call — sessions, OAuth, tools, resources, prompts, tasks, and more.

Features

  • Full MCP support: tools, prompts, resources, async tasks, skills, notifications, logging (stdio + Streamable HTTP)
  • Persistent sessions across multiple servers (stateful or stateless)
  • Progressive tool discovery to save tokens
  • Code mode: JSON output works with jq, xargs, and shell pipelines
  • OAuth 2.1 (CIMD + DCR) with OS keychain credential storage
  • MCP proxy for AI sandboxes (keep tokens away from generated code)
  • Lightweight CLI (Mac/Win/Linux) — no LLM required; experimental x402 payments on Base

Install

With homebrew (macOS and Linux), which brings its own Node.js:

brew install apify/tap/mcpc

or ,install the latest node js or Bun first, then:

npm install -g u/apify/mcpc
# Or with Bun
bun install -g /mcpc
npm install -g u/apify/mcpc

Quickstart

# List all active sessions and saved authentication profiles
mcpc

# Log in to a remote MCP server and save OAuth credentials for future use
mcpc login mcp.apify.com

# Create a persistent session and interact with it
mcpc connect mcp.apify.com 
mcpc               # show server info and capabilities
mcpc  tools-list   # list available tools
mcpc  tools-call search-actors keywords:="website crawler"

# Use JSON mode for scripting
mcpc --json  tools-list

# Use a local MCP server package (stdio) referenced from a config file
mcpc connect ./.vscode/mcp.json:filesystem 
mcpc u/fs tools-list
u/Impressive-Owl3830 — 1 month ago
▲ 88 r/MCPservers

OpenSource MCP of the week - 37k Stars - Playwright MCP - 100% free

I came across this amazing MCP related GitHub repo - 100% open source and free.

Playwright MCP is Microsoft's official MCP server for browser automation. It lets any LLM drive a real browser through the accessibility tree, no vision model or screenshots required.

GitHub repo in comments below.

featured in this week edition of MCPnewsletter.com

Features

- Fast, lightweight browser automation via Playwright's accessibility tree

- Works with Cursor, Claude Desktop, VS Code, Codex, and other MCP clients

- Headed or headless, persistent profiles, optional Docker

- Core tools for navigate, click, type, snapshot, plus optional PDF, vision, and DevTools caps

- Apache-2.0, ~36.6k GitHub stars

Install

{

"mcpServers": {

"playwright": {

"command": "npx",

"args": ["@playwright/mcp@latest"]

} } }

u/Impressive-Owl3830 — 1 month ago
▲ 93 r/MCPservers

OpenSource MCP repo of the day -28k stars Serena - 100% free

I came across this amazing MCP related GitHub repo - 100% open source and free.

Serena is an MCP toolkit that gives coding agents IDE-level powers: semantic symbol lookup, reference finding, and safer refactors instead of fragile text search-and-replace. It plugs into Claude Code, Codex, Cursor, and other MCP clients so agents work faster and more reliably on large codebases.

edit - GitHub repo - https://github.com/oraios/serena

Features

  • Semantic code retrieval at the symbol level (find symbol, references, file overview, diagnostics)
  • Symbolic editing and refactoring (rename, replace symbol body, insert before/after, safe delete)
  • Language server backend with support for 40+ programming languages (free/OSS default)
  • Optional JetBrains plugin backend for deeper analysis and interactive debugging
  • Memory system for long-lived agent workflows across sessions
  • Works with Claude Code, Codex, Cursor, VS Code, JetBrains, Claude Desktop, and more via MCP

How to Install

\`` uv tool install -p 3.13 serena-agent serena init ````

Then configure the Serena launch command in your MCP client (Claude Code, Codex, Cursor, etc.).

subscribe to MCPnewsletter.com for more MCP dev centric info and MCP related OSS repo's

u/Impressive-Owl3830 — 1 month ago
▲ 5 r/SEO

best place to look for SEO/AEO (or GEO) agency /directories?

Hey All,

looking for recomendations to find the best place to find the SEO agencies.

keen to work with an establish SEO agency who can drive result real results. Not looking for a solo expert.

An establish mid-tier firm with good results and they can drive the results for my clients.

What is the best way to find such an agencies? Is there any directories or WhatsApp groups where we can find them.

Also, how to evaluate them, any suggestions, recommendations would be appreciated.

reddit.com
u/Impressive-Owl3830 — 1 month ago
▲ 73 r/MCPservers

OpenSource MCP of the week - OmniMem - 100% free

I came across this amazing MCP related GitHub repo - 100% open source and free.

OmniMem is a self-hosted MCP memory server so your agent keeps project context, dead ends, and hard-won lessons across sessions. Runs on your hardware in Docker, MIT licensed, free forever.

GitHub repo - https://github.com/richarvey/OmniMem

Features

  • Five memory types: episodic, project, knowledge, preferences, skills
  • The Graveyard: abandoned approaches with why they failed
  • Experience scoring, contradiction detection, semantic dedup
  • One-call briefing() for session warm-up
  • Web UI plus Prometheus metrics
  • Works with Claude Code, Cursor, Copilot, Codex, and more

Install

curl -fsSL https://codeberg.org/ric_harvey/omnimem/raw/branch/main/install.sh | bash

Then point Claude Code at it (~/.claude.json):

{
  "mcpServers": {
    "omnimem": {
      "type": "sse",
      "url": "http://localhost:8765/sse"
    }
  }
}
u/Impressive-Owl3830 — 1 month ago
▲ 162 r/MCPservers

OpenSource MCP of the day- 27k stars- Blender MCP - 100% free

I came across this amazing MCP related GitHub repo - 100% open source and free.

Blender MCP connects Blender to any LLM so you can prompt-assist 3D modeling, scene creation, and manipulation. A Blender addon plus an MCP server let Claude, Cursor, and other clients drive objects, materials, and Python in your scene.

GitHub repo in comments below.

Features

  • Two-way communication between Claude/LLMs and Blender
  • Create, modify, and delete 3D objects
  • Apply and modify materials and colors
  • Inspect the current Blender scene
  • Execute Python code in Blender from your MCP client
  • Pull assets from Poly Haven, Sketchfab, Poly Pizza, plus AI models via Hyper3D and Hunyuan3D
  • MIT license, ~26.8k GitHub stars

Install

# 1. Install uv (macOS / Linux / Windows)
brew install uv
# or: curl -LsSf https://astral.sh/uv/install.sh | sh

# 2. Add MCP server (Claude Desktop config)
{
  "mcpServers": {
    "blender": {
      "command": "uvx",
      "args": ["blender-mcp"]
    }
  }
}

# 3. Install Blender addon
uvx blender-mcp install-addon

Then in Blender: Edit → Preferences Add-ons enable Interface: MCP for Blender.

Press N in the viewport MCP for Blender tab Start MCP Server.

u/Impressive-Owl3830 — 1 month ago
▲ 178 r/MCPservers

👀 OpenSource Repo of week -110k stars Graphify - 100% free

I came across this amazing GitHub repo - 100% open source and free.

Graphify is a Claude Code skill that reads a folder of code, PDFs, markdown, and screenshots, builds a knowledge graph, and can also start an MCP stdio server. About 71x fewer tokens per query than reading the raw files.

Post link / GitHub repo in comments below.

Features

  • /graphify on any folder: code, docs, papers, images
  • Multimodal: Claude vision on screenshots, diagrams, whiteboard photos
  • Interactive graph.html, Obsidian vault, optional wiki
  • Honest edges: EXTRACTED, INFERRED, or AMBIGUOUS
  • --mcp starts an MCP stdio server
  • Apache-2.0 / MIT, ~113k GitHub stars

Install

pip install graphifyy && graphify install

Then in Claude Code:

/graphify .

That's it. You get three files:

graphify-out/

├── graph.html open in any browser — click nodes, filter, search

├── GRAPH_REPORT.md the highlights: key concepts, surprising connections, suggested questions

└── graph.json the full graph — query it anytime without re-reading your files

u/Impressive-Owl3830 — 1 month ago
▲ 1 r/cofounderhunt

Looking for founder's with domain usecase of Doc processing

Hey,

We are team of 2 and looking for cofounder who are domain expert in any industry which require some sort of doc processing - like insurance , lawyer or logistics.

We are founders with strong track record. We built , raised and exit companies before ( Multi Million)

We build a strong agentic framework while building food industry product so looking to onboard a new domain use case and built and launch product in 8-10 weeks.

- i manage distribution and product management, my partner is expert software builder.

- co founder we looking for does not need to be technical just domain expert in thier respective industry. Ideally built products before.

- we seek Cash + Equity.

DM if you have a use case and willing to launch in 10 -12 weeks and willing to move and iterate fast.

Cheers.

reddit.com
u/Impressive-Owl3830 — 1 month ago
▲ 0 r/MCPservers

Anthropic launches Claude Fable 5.1 and Mythos 5.1

Claude Fable 5.1 / Mythos 5.1 (Sept 2026)

  • Same underlying model, different safeguard levels. Fable 5.1 is GA; Mythos 5.1 only via trusted access programs (Cyber Verification Program, Life Sciences Verification Program, the latter built with the US government). Claude Security now runs on Mythos 5.1.
  • Benchmark jumps, mostly on agentic and research work: Terminal-Bench-Science 52.6% (vs Fable 5 at 24.7%, Opus 5 at 29%), Terminal-Bench 4.0 55.8% Fable / 60.9% Mythos, CursorBench 73.4%, HLE 60.9% no tools, AutomationBench 31.4%. Partner quotes (Jane Street, Millennium, Cognition, Block) stress long-horizon reliability and readable output over multi-step runs.
  • ~25% cheaper than Fable 5 for typical token-billed workloads, up to ~45% on heavy agentic work, driven by cheaper cache reads. Defaults to High effort in Claude Code, Medium in Cowork and claude.ai.
  • Science results are the headline: protein binders with ~50% hit rate across 12 targets (10-15% is normal) and 10x affinity vs best Adaptyv Bio competition entries; a new Venus elevation map from 30-year-old Magellan radar released CC; custom GPU kernels giving up to 2.5x speedups on 7 open-source bio models, cutting genome-wide analysis GPU cost 30-60%.
  • Safeguards loosened where they were noisy: 60% fewer cyber interventions per Claude Code session, vulnerability discovery now allowed (exploit dev, pentesting, binary scanning still redirect to Opus), biology false positives down 85%. Plus Enterprise Frontier Safeguards (customer-controlled cloud storage, ZDR-equivalent, phased rollout this fall), new anti-distillation restrictions on editing prior context for new API accounts, and an EU AI Act text watermark with a detection API in private preview.
u/Impressive-Owl3830 — 1 month ago
▲ 2 r/MCPservers

Awesome hack - Managed to run MiniMax H3 at 0.16$/min on Nosana - this video cost 0.03$

MiniMax H3 is viral. Open weight - Video + native au

now i know why, the video quality is amazing.

But Mini Max API cost 7.50$/min - that's a lot which you are still experimenting. My goals is to try different formats and styles for my brand.

found this awesome hack - it turns out you can run Minimax H3 on Nosana by renting RTX 5090 cheaply- then keep prompting for new styles.

I made this video for 0.03$ for 15 secs one - could pay easily upto 90 cents to 1.2$ for same in directly via minimax API or any other tool.

sharing link and details in comments for those who wanna try.

u/Impressive-Owl3830 — 1 month ago
▲ 127 r/MCPservers

🔥 OpenSource MCP of the day -47K stars- GitNexus - 100% free

I came across this amazing MCP related GitHub repo - 100% open source and free.

GitNexus indexes any codebase into a knowledge graph, every dependency, call chain, and execution flow, then exposes it through MCP so Cursor, Claude Code, and Codex stop missing code.

GitHub repo in comments below.

Features

  • 17 MCP tools: impact, trace, context, query, cypher, route_map, and more
  • Local CLI plus MCP, no server required
  • One-command index and editor setup
  • Web UI at gitnexus.vercel.app for quick repo chat
  • ~46k GitHub stars
  • PolyForm Noncommercial license

Install

npx gitnexus analyze
npx gitnexus setup
u/Impressive-Owl3830 — 1 month ago
▲ 0 r/vibecodingcommunity

OpenSource vibecoding of the day - session-migrate - 100% free

I came across this amazing vibecoding related GitHub repo - 100% open source and free.

session-migrate moves a coding-agent session to another harness in one command when you hit a usage limit. Claude Code, Codex, Pi, Cursor, Grok, and more.

Post link / GitHub repo in comments below.

Features

  • 15+ harnesses, 225 routes
  • inspect without dumping the conversation
  • catalog search by title, name, or UUID
  • preserves messages, tool calls, and images when both sides support them
  • MIT, smigrate shorthand

Install

curl -LsSf https://session-migrate.github.io/install.sh | sh

Then: smigrate transfer SESSION_UUID --from claude --to codex --cwd "$PWD"

u/Impressive-Owl3830 — 2 months ago