← Back to entities

MCP Server

project 2700c5579595313a

Normalized: mcp server

moreland_contracts

Entity Properties (gold project table)

project_id

2700c5579595313a

name

MCP Server

client_id

—

billable_rate

—

canonical_metadata

—

created_at

2026-10-16 02:28:50.263980+00:00

updated_at

2026-10-16 02:28:50.263980+00:00

status

—

billable

—

recurring

—

squad

—

qa_partner

—

project_manager

—

lead_dev

—

description

—

state

—

team_name

—

closedate

—

dealstage

—

contract_type

—

contract_hourly_rate

—

contract_estimated_hours

—

contract_total_fee

—

alias_name

Employee Portal (3)

project_manager_alias

—

lead_dev_alias

—

qa_partner_alias

—

40%

Moderate — a somewhat similar entity exists

100%

Strong source linkage

Source Mappings (2)

	Source	Source ID	Display Name	Confidence	Method	Status
	moreland_contracts	c7bb9f8d1b8d31832b311b394b1cc0bd	MCP Server	1.00	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash c7bb9f8d1b8d31832b311b394b1cc0bd file_name ACP_MCP_Server_Arrangement_Letter.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B2FBDC96E-B70E-40A0-9092-E5DD743585EC%7D&file=ACP_MCP_Server_Arrangement_Letter.docx&action=default&mobileredirect=true company Air Control Products, Inc. project_name MCP Server contact_person Michael Greene contract_type fixed_fee hourly_rate — estimated_hours 200.0 total_fee_estimate 43000.0 brief_project_description Assisting with the design, build, and deployment of a Model Context Protocol (MCP) Server. start_date 2026-11-01 extracted_at 2026-10-30T02:05:37.808315+00:00 raw_text_preview October 14, 2026 Dear Michael Greene: MorelandConnect LLC (“Moreland”) is pleased to provide this Arrangement Letter (“Agreement”) confirming our consulting services (the “Services”) to assist Air Control Products, Inc. (“Client”) with the design, build, and deployment of a Model Context Protocol (MCP) Server — a secure, read-only natural-language interface that allows ACP users to query approved business data through Claude, backed by a governed Cube semantic layer and a private business API, and hosted in ACP’s QA environment. Project Approach Air Control Products will prioritize work and communicate with the Moreland team using normal communication channels (e.g., email, phone, meetings). The Moreland team will work with Air Control Products to coordinate the discovery, implementation, testing, and review of the MCP Server, confirming key technical dependencies in discovery before build begins. Responsibilities The following table outlines the key responsibilities for Air Control Products and Moreland. Moreland will perform the Services remotely and at Air Control Products’ office locations as needed. Overview This engagement delivers a secure, read-only MCP Server on Air Control Products’ own Azure infrastructure. Claude connects to a single remote MCP endpoint over HTTPS; users authenticate through Microsoft Entra ID; a private business API enforces tool- and data-level authorization; and a Cube semantic layer answers analytical requests from approved Synapse Serverless SQL views over published Gold data. Only the HTTPS MCP endpoint and OAuth discovery routes are exposed — the API, Cube, PostgreSQL, and data services remain private. Discovery and validation are built into the start of the engagement, and UAT, deployment, and handoff are built into the end. Estimated Timeline: Kickoff November 1, 2026; completion by December 20, 2026 (200 hours) Discovery & Validation (1A) — November 1 – November 13 (~30 hours) Build (1B–1D) — November 16 – December 11 (~1 file_created_at 2026-10-14T20:24:28+00:00 file_modified_at 2026-10-14T20:23:55+00:00 created_by Paul Franke modified_by Paul Franke _dlt_meta —
	moreland_contracts	3e3a4c9c832c76bfe2eaf808f904e864	MCP Server	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 3e3a4c9c832c76bfe2eaf808f904e864 file_name ACP_MCP_Server_Arrangement_Letter.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7BA365B5AB-CDF7-4A94-BC73-8E529C042775%7D&file=ACP_MCP_Server_Arrangement_Letter.docx&action=default&mobileredirect=true company — project_name — contact_person — contract_type fixed_fee hourly_rate — estimated_hours 200.0 total_fee_estimate — brief_project_description — start_date — extracted_at 2026-10-31T02:10:12.234795+00:00 raw_text_preview October 14, 2026 Dear Michael Greene: MorelandConnect LLC (“Moreland”) is pleased to provide this Arrangement Letter (“Agreement”) confirming our consulting services (the “Services”) to assist Air Control Products, Inc. (“Client”) with the design, build, and deployment of a Model Context Protocol (MCP) Server — a secure, read-only natural-language interface that allows ACP users to query approved business data through Claude, backed by a governed Cube semantic layer and a private business API, and hosted in ACP’s QA environment. Project Approach Air Control Products will prioritize work and communicate with the Moreland team using normal communication channels (e.g., email, phone, meetings). The Moreland team will work with Air Control Products to coordinate the discovery, implementation, testing, and review of the MCP Server, confirming key technical dependencies in discovery before build begins. Responsibilities The following table outlines the key responsibilities for Air Control Products and Moreland. Moreland will perform the Services remotely and at Air Control Products’ office locations as needed. Overview This engagement delivers a secure, read-only MCP Server on Air Control Products’ own Azure infrastructure. Claude connects to a single remote MCP endpoint over HTTPS; users authenticate through Microsoft Entra ID; a private business API enforces tool- and data-level authorization; and a Cube semantic layer answers analytical requests from approved Synapse Serverless SQL views over published Gold data. Only the HTTPS MCP endpoint and OAuth discovery routes are exposed — the API, Cube, PostgreSQL, and data services remain private. Discovery and validation are built into the start of the engagement, and UAT, deployment, and handoff are built into the end. Estimated Timeline: Kickoff November 1, 2026; completion by December 20, 2026 (200 hours) Discovery & Validation (1A) — November 1 – November 13 (~30 hours) Build (1B–1D) — November 16 – December 11 (~1 file_created_at 2026-10-14T20:26:01+00:00 file_modified_at 2026-10-14T20:25:59+00:00 created_by Paul Franke modified_by Paul Franke _dlt_meta —

MCP Server

Source Mappings (2)

Reassign Source Record

Add Source Mapping