Scope
Server Details
Scope keeps a freelancer’s approved scope, rates, deadlines, and change orders, then lets an assistant read that record before it answers. A 14-day trial, then Pro. The price is only at checkout.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 9 tools
Each tool targets a distinct resource+action: approve_change_order vs approve_scope operate on different objects, and save_deadline/save_rate/save_scope_item cover separate fields. The one subtle area is that save_scope_item (adding work) and file_change_order (kind add_work) both touch scope, but descriptions explicitly delineate that boundary.
Consistent verb_noun snake_case pattern throughout: approve_change_order, approve_scope, create_engagement, file_change_order, get_approved_record, list_engagements, save_deadline, save_rate, save_scope_item. No deviations or mixed conventions.
Nine tools is well-scoped for a focused freelancer scope/engagement domain, with each tool earning its place across draft, approval, and change-order workflows. No redundant or filler tools.
The surface covers the core lifecycle: create engagement, list, read approved record, manage scope items, rates, deadlines, and file/approve change orders. Minor gaps exist (no engagement update/delete, no way to remove an item or rate), but agents can work around these.
Available Tools
9 toolsapprove_change_orderapprove change orderADestructiveIdempotentInspect
Apply one proposed change order after the freelancer explicitly approves that order. Pass confirmed true only then. This is the path that may discount a rate or add work. Calling it is not a substitute for the freelancer's approval.
Inputs: confirmed (required), engagementId (required), changeOrderId (required). Returns: data
approve_scopeapprove scopeADestructiveIdempotentInspect
Mark the current draft as the approved scope. Pass confirmed true only after the freelancer explicitly approves the current items, rates, and deadlines.
Inputs: confirmed (required), engagementId (required). Returns: data
create_engagementcreate engagementBInspect
Create a draft engagement. Draft terms are not an approved commitment until approve_scope.
Inputs: title (required), currency (required), clientName (required), summary. Returns: data
file_change_orderfile change orderAInspect
Record a proposed change order. This does not change scope, rates, or deadlines. kind add_work requires workTitle and workDescription. kind discount_rate requires rateCode and a lower amountMinor. kind add_rate requires rateCode, rateLabel, amountMinor, and unit. kind move_deadline requires scopeItemId and dueOn.
Inputs: kind (required), summary (required), engagementId (required), unit, +7 more. Returns: data
get_approved_recordget approved recordARead-onlyIdempotentInspect
Read the approved scope, rates, deadlines, and change orders before answering. Quote only this record. Draft status is not an approved commitment. Proposed change orders do not authorize a discount or extra work.
Inputs: engagementId (required). Returns: data
list_engagementslist engagementsARead-onlyIdempotentInspect
List the signed-in freelancer's engagements. Use a returned id with get_approved_record. Do not guess an engagement.
Inputs: offset. Returns: data
save_deadlinesave deadlineBDestructiveInspect
Set or move the deadline for one scope item. The date is a calendar day in YYYY-MM-DD form.
Inputs: dueOn (required), scopeItemId (required), engagementId (required). Returns: data
save_ratesave rateADestructiveInspect
Set a draft rate, or update an approved rate without lowering it or changing its unit. A lower amount is a discount and is refused. A new rate code after approval is refused. Use file_change_order and approve_change_order for those.
Inputs: code (required), unit (required), label (required), amountMinor (required), +1 more. Returns: data
save_scope_itemsave scope itemADestructiveInspect
Add or update a scope item the freelancer has accepted. After approval, a new item is refused until approve_change_order adds that work. Renaming approved work is refused.
Inputs: title (required), description (required), engagementId (required), scopeItemId. Returns: data
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceRemote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.MIT
- AlicenseCqualityCmaintenanceCompetitor Monitor AI - MCP server providing AI-powered tools and automation by MEOK AI Labs112 npm37 PyPIMIT
- AlicenseAqualityDmaintenanceEnables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.1611 npm1MIT

industrylens-mcpofficial
AlicenseNot gradedqualityCmaintenanceBrowse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.