# Linklamp

> An MSP describes a switch swap or repatch at a Dearborn, Michigan client site (and can paste its port map). The page drafts the visit scope: on-site duties, what the MSP's remote engineer keeps, exclusions (new electrical circuits or outlets, fire alarm systems, new cable runs, switch configuration) and the questions that change price or duration. Requesting the proposal records the requirement with a reference; Linklamp then emails a proposal with visit duties, exclusions, price and a proposed time. Nothing is booked or priced until the MSP accepts. The client's window can also be sent as an appointment request, which a provider confirms or not on its status page.

Site: https://linklamp.meetinggrove.com/

## Pages

- [Linklamp: switch swaps and repatching in Dearborn, MI, for MSPs](https://linklamp.meetinggrove.com/index.md): Hands at the rack in Dearborn, MI while your engineer runs the cutover: switch swap or repatch, port photos before and after, done when your engineer signs off. Draft the visit, get a proposal by email.
- [How a Linklamp visit runs: port photos, signoff, rollback](https://linklamp.meetinggrove.com/visit/index.md): How a Linklamp switch swap or repatch visit runs in Dearborn, MI: your engineer keeps configuration and signs off, every labelled port is photographed before and after, and rollback is planned.
- [What a closet visit can and cannot touch | Linklamp](https://linklamp.meetinggrove.com/boundaries/index.md): Switch swap and repatch visits in Dearborn, MI: what is telecom equipment work, why a new outlet needs an electrician, why fire alarm dialers are left as they are, and how new cable drops are priced separately.
- [Your Linklamp visit request](https://linklamp.meetinggrove.com/status/index.md): The private view of a recorded Linklamp visit request: the recorded scope, open questions and what happens next.

## What you can do

- Send a requirement: POST https://linklamp.meetinggrove.com/_c/request with the envelope in https://linklamp.meetinggrove.com/openapi.json (or the MCP tool submit_request). The request is recorded with a reference at once. Linklamp reads the scope, open questions and any words kept as written, then prices and schedules the visit and emails a proposal: visit duties, exclusions, price and a proposed time inside the client's window. Without an email address the request is still recorded, reply_by_email is listed in missing_specifications, and no proposal can be sent until an address is given in a continuation. Nothing is ordered, booked or committed until the buyer agrees terms; a time is confirmed only on the appointment status page, after a provider confirms it. Contact details are kept apart from the requirement, while we correspond or do business and for 24 months after, so a later request picks up where it left off; ask us to delete them at any time.
- Ask for an appointment (Closet visit, Dearborn): POST https://linklamp.meetinggrove.com/_c/appointments. A requested time is a request; it is confirmed only when the provider confirms it, and the status link says which.

- Resume a requirement with request_status using its receipt id and token. Send additional requirements with continuation: {id, token}. Linked authorized offers appear in request_status; inspect_offer, accept_offer, decline_offer and release_payment use the same customer HTTP operations. counter_offer proposes a change (a proposal, not a change), submit_purchase_order sends a purchase order to be matched against the terms, state_purchasing_requirements and report_vendor_status say how the buyer's purchasing works, inspect_delivery records what was accepted and rejected, and answer_remedy answers a proposed remedy: each is recorded on the exact terms hash and answered by the business in inspect_offer's thread. Keep private credentials for later visits. Payment links lead to the processor; inspect_offer reports verified payment state.

## Machine interfaces

- [OpenAPI](https://linklamp.meetinggrove.com/openapi.json)
- MCP (streamable HTTP, stateless): https://linklamp.meetinggrove.com/mcp

## Connect from your agent

The MCP endpoint is https://linklamp.meetinggrove.com/mcp (Streamable HTTP, stateless, no sign-in). Adding it in one host does not add it in another.

- Claude (claude.ai, desktop and mobile): In Claude, open Customize, then Connectors, choose Add custom connector and enter https://linklamp.meetinggrove.com/mcp with no sign-in.
- ChatGPT: In ChatGPT on the web, open Plugins, choose + and Add custom MCP server, and enter https://linklamp.meetinggrove.com/mcp with no authentication, where your plan allows custom servers.
- Claude Code: Add it from a terminal:

  ```
  claude mcp add --transport http linklamp https://linklamp.meetinggrove.com/mcp
  ```
- Codex: Add it to ~/.codex/config.toml:

  ```
  [mcp_servers.linklamp]
  url = "https://linklamp.meetinggrove.com/mcp"
  ```
- Gemini CLI: Add it from a terminal:

  ```
  gemini mcp add --transport http linklamp https://linklamp.meetinggrove.com/mcp
  ```
- Antigravity: Add it from a terminal:

  ```
  agy mcp add linklamp https://linklamp.meetinggrove.com/mcp
  ```
- Grok (grok.com and Grok CLI): On grok.com add a New Connector, Custom, with https://linklamp.meetinggrove.com/mcp; in Grok CLI:

  ```
  grok mcp add --transport http linklamp https://linklamp.meetinggrove.com/mcp
  ```
- VS Code (GitHub Copilot): Open the install link in VS Code, or run MCP: Add Server and enter https://linklamp.meetinggrove.com/mcp. vscode:mcp/install?%7B%22name%22%3A%22linklamp%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Flinklamp.meetinggrove.com%2Fmcp%22%7D
- Cursor: Open the install link in Cursor, or add https://linklamp.meetinggrove.com/mcp under MCP settings. cursor://anysphere.cursor-deeplink/mcp/install?name=linklamp&config=eyJ1cmwiOiJodHRwczovL2xpbmtsYW1wLm1lZXRpbmdncm92ZS5jb20vbWNwIn0%3D

## Who runs it

Linklamp is operated by Tempered Technologies LLC, 8 The Green STE B, Dover, DE 19901. Privacy: https://linklamp.meetinggrove.com/privacy/