MCP Server

Orbital provides a Model Context Protocol (MCP) server for programmatic access to content and services. AI agents can discover, browse, and interact with content through standardized tools and prompts.

Getting Started

Endpoint

https://orbital.co.nz/api/mcp

Protocol

MCP 1.0 over HTTP with JSON-RPC 2.0 messaging

Authentication

None required - public read access

Available Tools

list_posts

List all published posts (excludes drafts)

// Returns: Array of posts with title, slug, description, date, tags

list_posts_by_tag

Filter posts by specific tag

// Parameter: tag (string)
// Returns: Array of posts matching the tag

get_post

Retrieve full post content by slug

// Parameter: slug (string)
// Returns: Full post with metadata and HTML content

list_tags

Get all available tags

// Returns: Array of unique tags used across all posts

get_service_offerings

Get detailed service information with pricing and deliverables

// Returns: Pilot Project ($25-50K), Fixed-Fee Project ($80-160K),
// Ongoing Development ($8-12K/month) with full details

get_specializations

Get technical capabilities and tech stack details

// Returns: React interfaces (visualization, monitoring, dashboards)
// and AI systems (document intelligence, workflows, agents)

check_client_fit

Get ideal client criteria and qualification guidelines

// Returns: Good fit indicators, target sectors, anti-patterns
// Useful for qualifying leads and understanding ideal clients

get_pricing_summary

Get quick pricing reference for all engagement types

// Returns: Concise pricing overview with ranges and durations
// All pricing in USD, $25K minimum engagement

Example: Claude Desktop

Add to your Claude Desktop config:

{
  "mcpServers": {
    "orbital": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-fetch",
        "https://orbital.co.nz/api/mcp"
      ]
    }
  }
}

Use Cases

  • Content Discovery: AI agents can browse and recommend relevant articles
  • Research Assistant: Query specific topics across the knowledge base
  • Service Integration: Agents can guide users through service offerings
  • Automated Summaries: Generate overviews of content by topic

Technical Details

  • Transport: Streamable HTTP with JSON responses
  • Protocol: JSON-RPC 2.0 over MCP specification
  • Stateless: No session management required
  • Content Visibility: Respects same rules as web interface (drafts excluded from listings)
  • Error Handling: Comprehensive validation and error responses

Resources