News for hackers. Stuff that matters.

mywork-dev

Show HN: MCPShark adds config.toml support for Codex

Quick update: MCPShark now supports Codex’s config.toml.If you use Codex CLI / the Codex VS Code extension, MCPShark will auto-detect ~/.codex/config.toml (or $CODEX_HOME/config.toml), parse the [mcp_servers] entries, and convert them into MCPShark’s internal config automatically (stdio + HTTP supported).Repo: https://github.com/mcp-shark/mcp-sharkVS Code extension:...

( Read More... | no comments | 16 points | on HN )

Show HN: MCPShark Viewer (VS Code/Cursor extension)- view MCP traffic in-editor

A few days ago I posted MCPShark (a traffic inspector for the Model Context Protocol). I just shipped a VS Code / Cursor extension that lets you view MCP traffic directly in the editor, so you’re not jumping between terminals, logs, and "I think this is what got sent".VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=MCPShark...Main repo:...

( Read More... | no comments | 15 points | on HN )
Thank your comments. The primary purpose of this tool is currently for local development. But I would like to hear more about your pain points. Please open a discussion thread https://github.com/mcp-shark/mcp-shark/issues. Would love to hear more.

Show HN: MCPShark – Traffic Inspector for Model Context Protocol

https://github.com/mcp-shark/mcp-shark Site: https://mcpshark.sh/I built MCPShark, a traffic inspector for the Model Context Protocol (MCP).It sits between your editor/LLM client and MCP servers so you can: • See all MCP traffic (requests, responses, tools, resources) in one place • Debug sessions when tools don’t behave as expected • Optionally run “Smart Scan” checks to flag risky tools /...

( Read More... | 4 comments | 26 points | on HN )