# Effect Grep — Effect TypeScript examples and application graphs

Effect Grep provides read-only retrieval over pinned Effect reference repositories. Use it to discover source-backed improvement opportunities, find real API usage, and understand how Layers and Services compose. No authentication is required.

## When to use

- For improvement opportunities, call find_capabilities({}), browse responsibilities, then search ordinary application language with the caller's runtime and dependency versions. Investigate benefits and tradeoffs before proposing changes.
- For API examples, call find_examples with a symbol such as Effect.gen, then get_source to verify authored code.
- For composition, call list_repositories, choose a repository with graphAvailable, then get_application_graph and inspect_graph_part using returned keys.

## Connect

Connect a Streamable HTTP MCP client to /mcp. Discover tool schemas with tools/list. Preserve returned generation IDs on follow-ups and restart discovery on stale_generation. Cite pinned source links; partial evidence and unknown compatibility remain uncertain.

- [Workflow skill](/.well-known/agent-skills/effect-grep/SKILL.md)
- [Skill discovery](/.well-known/agent-skills/index.json)
- [MCP server card](/mcp/server-card)
- [HTTP API documentation](/api/docs)
- [OpenAPI contract](/openapi.json)
- [Readiness and generation](/api/status)
- [Published repositories](/api/repositories)

If MCP is unavailable, use the HTTP documentation and check readiness before retrieval. Capability discovery and bounded graph inspection are MCP tools; the HTTP fallback exposes corpus inventory, uses, source, and graph artifacts.