ovbslaught

7 mods across 1 repository, 5 stars between them.

perplexity

01

ovbslaught/NOMADZ-0

MCP server Claude CodeCodexCursor +2

One of 6 in mcp.json

Real-time web search, reasoning, and research through Perplexity's API. Runs locally from the @perplexity-ai/mcp-server npm package. Needs 1 environment variable to run.

not rated 5 yesterday A tokens not measured copy · 89% MIT

github

02

ovbslaught/NOMADZ-0

MCP server Claude CodeCodexCursor +2

One of 6 in mcp.json

GitHub's hosted MCP server: lets the agent search code, read and create issues and pull requests. Remote server at api.githubcopilot.com.

not rated 5 yesterday A tokens not measured copy · 100% MIT

filesystem

03

ovbslaught/NOMADZ-0

MCP server Claude CodeCodexCursor +2

One of 6 in mcp.json

Gives the agent read and write access to a set of allowed directories on the local filesystem. Runs locally from the @modelcontextprotocol/server-filesystem npm package.

not rated 5 yesterday A tokens not measured original MIT

firecrawl

04

ovbslaught/NOMADZ-0

MCP server Claude CodeCodexCursor +2

One of 6 in mcp.json

MCP server "firecrawl" as configured in ovbslaught/NOMADZ-0. Runs locally from the @mendableai/firecrawl-mcp-server npm package. Needs 1 environment variable to run.

not rated 5 yesterday A tokens not measured original MIT

notion

05

ovbslaught/NOMADZ-0

MCP server Claude CodeCodexCursor +2

One of 6 in mcp.json

Lets the agent search, read and edit pages and databases in a Notion workspace. Runs locally from the @notionhq/notion-mcp-server npm package. Needs 1 environment variable to run.

not rated 5 yesterday A tokens not measured copy · 94% MIT

gdrive

06

ovbslaught/NOMADZ-0

MCP server Claude CodeCodexCursor +2

One of 6 in mcp.json

MCP server for interacting with Google Drive. Runs locally from the @modelcontextprotocol/server-gdrive npm package. Needs 1 environment variable to run.

not rated 5 yesterday A tokens not measured original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: