Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/atlanhq/agent-toolkitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/atlanhq/agent-toolkit/mcp-guidelines)<a href="https://agentmods.dev/rules/atlanhq/agent-toolkit/mcp-guidelines"><img src="https://agentmods.dev/badge/rules/atlanhq/agent-toolkit/mcp-guidelines/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/atlanhq/agent-toolkit/mcp-guidelines"><img src="https://agentmods.dev/badge/rules/atlanhq/agent-toolkit/mcp-guidelines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00752 |
| Opus 5.5 | $0.00000 | $0.00301 |
| Sonnet 5.5 | $0.00000 | $0.00150 |
| Haiku 4.5 | $0.00000 | $0.00075 |
Grade A, and why
mcp-guidelines scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert in Python, Model Context Protocol (MCP), and Atlan integration.
Key Principles
- Write concise, technical responses with accurate Python examples for Atlan integration.
- Use modular, well-structured code with clear separation of concerns.
- Implement proper error handling and logging for robust API communication.
- Use descriptive variable names that reflect domain terminology.
- Follow Atlan and Model Context Protocol best practices.
- Create reusable utility functions for common operations.
Python/MCP/Atlan Guidelines
- Use FastMCP for server implementation with clear tool definitions.
- Leverage PyAtlan's rich API for communicating with Atlan services.
- Use type hints for all function signatures, especially for complex Atlan objects.
- Implement proper error handling with appropriate logging.
- Use environment variables for configuration using Pydantic's BaseSettings.
- Structure code with client initialization, tool definitions, and execution handlers.
Code Structure
- Separate server configuration from tool implementations.
- Create dedicated client factory functions for Atlan API interactions.
- Implement consistent logging throughout the application.
- Follow the pattern of defining tools with descriptive docstrings for automatic MCP tool generation.
- Use type annotations compatible with both PyAtlan and MCP.
Atlan-Specific Guidelines
- Use PyAtlan classes ( eg Asset, Table, Column) for type checking and accessing model attributes.
- Implement FluentSearch for complex asset queries with flexible conditions.
- Use CompoundQuery for common filter patterns like active assets.
- Support pagination for large result sets.
- Handle proper error cases for Atlan API responses.
- Implement rich filtering options (conditions, negative conditions, some conditions).
- Support inclusion of specific attributes in results.
Error Handling and Validation
- Log all API requests and responses at appropriate levels.
- Implement comprehensive error handling:
- Catch and log exceptions from Atlan API calls.
- Return empty lists or default values for failed operations.
- Use descriptive error messages with contextual information.
- Include troubleshooting information in logs.
- Validate input parameters before constructing API requests.
Execution Model
- Use synchronous operations for Atlan API calls.
- Implement appropriate request timeout settings.
- Apply rate limiting for bulk operations.
- Use pagination for large result sets.
- Return well-structured responses that MCP can properly format.
Search Optimization
- Build search queries incrementally with appropriate logging.
- Support various search patterns: equality, containment, pattern matching.
- Implement efficient filtering strategies using PyAtlan's built-in operators.
- Support a wide range of search conditions including date ranges.
- Optimize complex queries with proper indexing strategies.
DSL Query Handling
- Validate and parse DSL JSON properly.
- Provide examples for common DSL patterns.
- Support various query structures like function_score and bool queries.
- Return both results and aggregations.
- Implement proper error handling for malformed DSL queries.
Tools and Utility Functions
- Create helper functions for common operations like:
- Query building
- Result formatting
- Error handling
- Attribute resolution
- Implement consistent patterns for handling Atlan's typed attributes.
Key Conventions
- Use PyAtlan's fluent interface for building search queries.
- Properly handle authentication and API errors.
- Implement appropriate logging at multiple levels:
- Debug for query construction details
- Info for operation completion
- Warning for non-critical issues
- Error for failures
- Follow MCP conventions for tool registration and execution.
- Provide rich documentation for tools with examples.
Dependencies
- mcp[cli] for MCP server implementation
- pyatlan for Atlan API integration
- pydantic-settings for configuration management
- logging for application logging
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 94 lines · 0 tokens per session scan A 896bb21aefd2
mcp-guidelines is a cursor rule published in the GitHub repository atlanhq/agent-toolkit (41 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 752 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
fenic
Cursor rule "fenic" from typedef-ai/fenic, covering writing fenic, must-knows and traps fenic check can't catch — get these right by hand.
02-python-standards
Python coding standards, libraries, and concurrency safety.
hatch3r-python-patterns
Python 3.12+ conventions covering uv project management, Ruff lint+format, mypy strict typing, pytest parametrize, and the FastAPI/Django request-path + ORM N+1 floor.
backend-python
Cursor rule "backend-python" from coeusyk/inference-x, covering backend python rules, stack assumptions, code style, fastapi conventions and schema conventions.
react-vite-tanstack
You are an expert in TypeScript, Node.js, React, Vite, Yarn ,TanStack Query, TanStack Router, Tanstack table, Tanstack form ,Shadcn elements and Tailwind.
pn-go-backend
Go backend style, env, and error handling. Use for API and server code (Gin, Fiber, Echo).