ParcelOps Skills API and MCP server

API access

Your AI client reaches ParcelOps Skills through one ParcelOps MCP endpoint, so there is no separate key to hold for it and no per-source client to write. Reaching it takes no credentials of your own.

What this source cannot tell you

• ⚠ Where it stops geographically, because the covered area is not declared. An empty answer will not tell you whether the place is out of range or the record is simply missing.
• ⚠ Which years it spans, because the covered period is not declared.
• ⚠ How current a field is, because the refresh schedule is not declared.
• ⚠ Anything ParcelOps Skills does not publish. ParcelOps returns this source as it stands and never fills a blank field from a different one.

Methods (3)

A method is one call your agent can make against this source.

• listSkills

  read

  List active ParcelOps skills.

  Input schema

  {
    "type": "object",
    "properties": {},
    "required": [],
    "additionalProperties": false
  }

• getSkill

  read

  Get a skill by slug.

  What you must provideslug
  Input schema

  {
    "type": "object",
    "properties": {
      "slug": {
        "type": "string"
      }
    },
    "required": [
      "slug"
    ],
    "additionalProperties": false
  }

• getSkillInstructions

  read

  Return LLM-ready instructions for a skill.

  What you must provideslug
  Input schema

  {
    "type": "object",
    "properties": {
      "slug": {
        "type": "string"
      }
    },
    "required": [
      "slug"
    ],
    "additionalProperties": false
  }