using portable `~` paths. Edit directly without rebuild.
**MCP architecture:** Uses 1MCP to aggregate all MCPservers. Server definitions are in
`configs/claude/1mcp.json` (symlinked to `~/.config/1mcp/mcp.json`). CLI connects to 1MCP
via `claude
been written yet this session.
## MCP Steroid — IntelliJ IDE Control
When the `localhost-6315` MCPserver (mcp-steroid) is connected, its skill guides are exposed as MCP resources and fetched
Development Commands
- `npm install` - **ALWAYS run first** to install dependencies
- `npm start` - Start the MCPserver
- `npm run auth-server` - Start the OAuth authentication server on port 3333 (**required
goal?"** — For any activity
2. **"Did this increase leverage?"** — For any output
---
## Part 11: MCPServers
### Connected Servers
| Server | Status | What It Enables |
|--------|--------|-----------------|
| Gmail | Connected | Email triage, drafting |
| Google Calendar
before the server so `server/internal/api/ui/dist` contains the files required by `go:embed`.
## Core invariants
- Node IDs are deterministic SHA-256 identities. Config and MCP collection must emit the same MCPServer
this repo until that is done.
You have access to a `memstack-skills` MCPserver. This is your **PRIMARY** source for task-specific guidance. ALWAYS check memstack-skills via `find
boost rules ===
## Laravel Boost
- Laravel Boost is an MCPserver that comes with powerful tools designed specifically for this application. Use them.
## Artisan
- Use the `list-artisan-commands` tool when
healthcare plugin — conventions
- **Local data**: skills and bundled MCPservers write to `~/.claude/data/healthcare/ /`, where the component is the *server's* name, not the skill's (the contracts skill's server
github.copilot.chat.agentDebugLog.fileLogging.enabled`
### MCP Across Agent Types
- **MCP support in Copilot CLI and Claude agents** - MCPservers registered in VS Code are now bridged into Copilot CLI and Claude agent workflows, including
working in this repository.
This is the **upstream source** for `odoo-mcp` — the Odoo MCPserver published
to PyPI as `odoo-mcp` (`uvx odoo-mcp`) and consumed by downstream projects
Frontend work**: Study component patterns in `WORKBENCH_FRONTEND.md`
* **API development**: Follow service patterns from `WORKBENCH_SERVICE.md`
* **MCPservers**: Use existing servers in `MCP_SERVERS.md` as templates
* **AI tools**: Provide relevant context files
install and use file search tools for best results. If needed, use the docs MCPserver as defined in `.mcp.json` for programmatic access.
- **Contributing Guide:** [`.github/CONTRIBUTING.md`](https://docs.langchain.com/oss/python/contributing/overview)
# Google
BlockRun MCPMCPserver giving Claude real-time data — markets, research, web search, crypto. Pay per call with USDC.
## Commands
```bash
npm install # install dependencies
npm run build # compile with
Kubernetes**: kubectl, kubernetes SDK
## Issue tracking (Linear)
This repo ships a **project-scoped** Linear MCPserver in `.mcp.json` named `linear-grc-club`, pointing at `https://mcp.linear.app/mcp`. It loads only
else `--version` build id) instead of trusting the first PATH hit.
**MCP** (`engine/laya/mcp/`): HTTP/SSE MCPserver exposing Laya tools to external agents. Scope-filtered per user settings, space-aware
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.