# Noosphere

Hooks a coding agent up to a live registry of reviewed engineering skills, so it can match a real failure, verify the artifact and apply it.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 18
- Author: JinNing6
- License: Apache-2.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/JinNing6/Noosphere
- Updated: 2026-10-19
- HTML: https://affpapa.org/en/nevibecode/mcp/noosphere

## What it does

Noosphere is an MCP server that points your agent at a GitHub-hosted registry of skills. A concrete bug shows up; the agent looks for a published skill that covers it, checks the exact artifact against its SHA-256 digest, tests whether it fits the local setup, applies it, and runs the project's own verification before reporting a fix.

The bundle carries one control skill, `using-noosphere`, rather than frozen copies of every engineering skill. Approved skills stay in the registry, so each newly reviewed release reaches every connected agent with no plugin reinstall. Anonymous lookups are read-only. Writing public evidence, withdrawing a skill, or posting to the consciousness side needs authentication plus user consent at the moment of the write.

Registry access runs on a GitHub token in `GITHUB_TOKEN`; the repository goes in `NOOSPHERE_REPO`. Skip the token and you keep anonymous search only, for instance `uvx --from noosphere-mcp noosphere-query` with a description of the failure.

## Requirements
- Needs: Python and uv (commands run via uvx)
- Environment variables: `GITHUB_TOKEN`, `NOOSPHERE_REPO` — keys and tokens: ask the human for the values, never commit them or put them in shared files.

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add --env GITHUB_TOKEN=<GITHUB_TOKEN> --env NOOSPHERE_REPO=<NOOSPHERE_REPO> --transport stdio noosphere -- uvx noosphere-mcp
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from noosphere-mcp <command>

### Codex

**Platform CLI**
```bash
codex mcp add noosphere --env GITHUB_TOKEN=<GITHUB_TOKEN> --env NOOSPHERE_REPO=<NOOSPHERE_REPO> -- uvx noosphere-mcp
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from noosphere-mcp <command>

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "noosphere": {
            "command": "uvx",
            "args": [
                "noosphere-mcp"
            ],
            "env": {
                "GITHUB_TOKEN": "<GITHUB_TOKEN>",
                "NOOSPHERE_REPO": "<NOOSPHERE_REPO>"
            }
        }
    }
}
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from noosphere-mcp <command>

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "noosphere": {
            "type": "stdio",
            "command": "uvx",
            "args": [
                "noosphere-mcp"
            ],
            "env": {
                "GITHUB_TOKEN": "<GITHUB_TOKEN>",
                "NOOSPHERE_REPO": "<NOOSPHERE_REPO>"
            }
        }
    }
}
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from noosphere-mcp <command>

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add -e GITHUB_TOKEN=<GITHUB_TOKEN> -e NOOSPHERE_REPO=<NOOSPHERE_REPO> noosphere uvx noosphere-mcp
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from noosphere-mcp <command>

## When to use it
- locate a reviewed skill that matches a specific bug
- check a skill artifact by SHA-256 before applying it
- decide whether a skill fits the local project
- run real verification after an agent applies a fix
- search the registry with no clone and no account

## Example prompts
- Find a Noosphere skill for the failing CI build and show its SHA-256.
- Check whether that skill applies to my repo, then run the verification after applying it.
- Search the registry for this: tapping a mobile 3D node selects the wrong instance.

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 386989
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33918
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81115
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119160
- [Codebase Memory](https://affpapa.org/en/nevibecode/mcp/codebase-memory.md) — MCP server · ★ 47392
- [mcp-server](https://affpapa.org/en/nevibecode/mcp/mcp-server.md) — MCP server · ★ 43872

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md