Method CRM MCP Server for Cloudflare Workers with OAuth 2.1. Provides tools for interacting with Method CRM API including table operations, record management, field discovery, and more.
The server defines 19 tools with generally clear names following verb_noun conventions (method_tables_query, method_tables_create, etc.). Most tools have descriptions and parameter schemas, but quality is inconsistent. Descriptions range from good (60-100 chars) to adequate, with several tools missing critical context about side effects and error recovery. Parameter schemas are present with type information, but many lack format constraints, ranges, or detailed instructions on valid values. Output schemas are undocumented, no indication of what fields are returned or pagination structure. Error handling guidance is minimal. Security-critical issues include _skip_confirmation parameters that bypass safety checks and insufficient validation warnings.
Create a new activity for a record in Method CRM
List activities for a record in Method CRM
Execute multiple operations in a single batch request to Method CRM
List events for a record in Method CRM
List files attached to a record in Method CRM
Upload a file to Method CRM
Bulk import records into a Method CRM table
Output schemas completely undocumented. No tool declares what fields are returned, data types, or structure of response objects. LLMs cannot plan downstream tool calls without knowing what data is available.
_skip_confirmation parameter on destructive operations is a severe security/safety anti-pattern. This boolean flag allows LLMs to bypass safety prompts, enabling accidental data loss. Confirmation should be enforced server-side via user-gate patterns, not client-controlled flags.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2026-07-28+ | v2 |
Create a relationship between two records in Method CRM
Delete a relationship between two records in Method CRM
List relationships for a record in Method CRM
Execute a routine (workflow/automation) in Method CRM
Create a new record in a Method CRM table
Delete a record from a Method CRM table
Discover fields and schema information for a Method CRM table
Retrieve a single record from a Method CRM table by record ID
List all available tables in the Method CRM instance
Look up valid values for a reference field in a Method CRM table
Query records from a Method CRM table with filtering, pagination, sorting, and expansion options
Update an existing record in a Method CRM table
Destructive operations (create, update, delete, batch, import) lack clear descriptions stating that they modify state. LLMs need explicit warnings about side effects to plan safely. Descriptions should say 'Creates a new record' not just 'Create a new record in a Method CRM table'.
Parameter validation guidance is minimal. Many parameters (filter, orderby, field_name, routine_id) lack format constraints, allowed values, or examples. The OData filter expression in method_tables_query has no description of OData syntax or valid operators.
Pagination parameters exist (top, skip, limit) but no total count, next_cursor, or has_more flag is documented. LLMs cannot determine if more results exist or how to fetch them.
No error handling guidance in tool descriptions. LLMs receive no indication of common failure modes (invalid table name, authentication failure, duplicate record, rate limit) or how to recover.
method_batch_operations and method_import_records lack descriptions of their operations array structure. No indication of what operations are supported, what fields each operation requires, or format of the array.
No permission/scope declarations on tools. LLMs cannot know what permissions are required, blocking least-privilege configurations. Sensitive operations like delete should declare required scopes.
table parameter is free-form string across all tools with no guidance on valid table names. No discovery tool or schema documentation indicates what tables exist or their naming convention. LLMs must guess or query method_tables_list first.
response_format parameter is enum ['json', 'markdown'] but LLMs have no guidance on when to use which format. Tool responses should be structured consistently; if markdown is needed, provide structured data and let the client format for display.