Tag

#develop

444 results found

Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Memtrace
@syncable-dev

Memtrace — Structural Memory for AI Coding Agents The Problem Every AI coding agent — Claude Code, Cursor, Codex, Copilot — starts each turn completely blank. It re-reads raw source files and re-derives the full call graph, type hierarchy, and import tree from scratch on every single invocation. That structural rework burns 60–90% of the context window before any real reasoning begins. Less than 5% of tokens in a typical agentic coding session contribute genuine new intelligence. The rest is expensive, redundant noise — and it compounds: accuracy drops 40% as sessions grow, stale context crowds out signal, and summaries strip out the structural relationships agents need most. The Solution Memtrace is a bi-temporal structural memory layer that turns your codebase into a live, queryable knowledge graph — compiled from the AST, not guessed from embeddings. Every function, class, interface, and API endpoint becomes a typed node with deterministic relationships. Every file save becomes a queryable episode with timestamps, so agents can reason about structure, detect regressions, and time-travel through their own work without re-reading anything. One Rust binary. Zero configuration. Five-minute install. What agents can do with it Find callers, callees, and dependencies instantly — no file scanning, no token waste Compute blast radius before making a change — know exactly what breaks before anything is touched Detect structural drift between sessions — catch regressions the moment they happen, not at PR review Time-travel through code evolution — query any prior state of any symbol, not just git commits Search across the full codebase with hybrid retrieval — BM25 full-text + HNSW vector + graph traversal fused in one query Map API topology across services — cross-repo HTTP call graphs, dependency chains, dead endpoint detection Benefits −90% token cost on structural queries (Mem0) +26% accuracy on multi-step agentic tasks (Mem0) −91% p95 latency on structural lookups vs. RAG baselines +32.8% SWE-bench bug-fix success rate when agents have graph context (RepoGraph) 200–800ms per-save re-indexing — every file save is a queryable episode in under a second 40+ MCP tools covering indexing, search, relationships, impact analysis, temporal evolution, API topology, graph algorithms, and direct Cypher queries 12 languages + 3 IaC formats supported via Tree-sitter grammars Local-first, closed-source Rust — code never leaves the machine, no account required, no telemetry

a month ago
Chain.Love MCP
@Chain.Love

## Overview ### what is Chain.Love MCP? Chain.Love MCP is a hosted remote MCP server and gateway for AI agents. It provides a single endpoint for discovering and comparing Web3 infrastructure services across 50+ blockchain networks, including RPCs, indexing, oracles, storage, compute, and developer tools. ### how to use Chain.Love MCP? To use Chain.Love MCP, add the hosted endpoint to your MCP client and connect to `https://app.chain.love/mcp` over Streamable HTTP. For public use cases, the basic MCP server URL is enough. For private downstream MCPs, add credentials only when required using `x-chainlove-cred-<credentialKey>` headers. ### key features of Chain.Love MCP? - Hosted remote MCP gateway for AI agents - Single endpoint for Web3 infrastructure discovery across 50+ blockchain networks - Aggregates infrastructure options across RPCs, indexing, oracles, storage, compute, and developer tools - Streamable HTTP transport - Public documentation and onboarding resources available online ### use cases of Chain.Love MCP? - Discovering and comparing Web3 infrastructure providers across many blockchain networks - Finding RPC, indexing, oracle, storage, compute, and developer tooling options through one MCP server - Giving AI agents a single hosted integration surface for Web3 infrastructure discovery - Reducing the need to integrate many separate provider-specific endpoints ### FAQ from Chain.Love MCP? - Can Chain.Love MCP be used as a hosted remote MCP server? Yes. Chain.Love MCP is designed to be consumed as a hosted remote MCP endpoint at `https://app.chain.love/mcp`. - Does Chain.Love MCP require credentials? Not always. Some downstream integrations may require credentials, which can be passed using `x-chainlove-cred-<credentialKey>` headers when needed. - How do I know which credential header to use? You can check the open-source Chain.Love registry at `https://github.com/Chain-Love/chain-love/blob/main/references/offers/mcpservers.csv` or browse `https://app.chain.love/toolbox/mcpservers` and look for the relevant `credentialKey` value. - Where can I learn more? Landing page: `https://www.chain.love/mcp-gateway` Documentation: `https://chain-love.gitbook.io/mcp-module`

2 months ago