Strike48 Labs Strike48 Labs

Connectors

Connectors are external services that integrate with Prospector Studio over a persistent gRPC bidirectional stream. They provide tools, data pipelines, and even full web UIs to the platform.

What Are Connectors?

Connectors extend Prospector Studio by registering capabilities over gRPC. Unlike MCP Servers which use stateless HTTP, connectors maintain a persistent connection and support richer interaction patterns.

A connector can implement one or more behaviors:

Behavior Description
Tool Provide callable functions for AI agents
Source Pull-based data ingestion (query, stream with cursor)
Sink Push-based data export to external systems
Request/Response Synchronous RPC operations
Pub/Sub Continuous event streaming
App Serve a full web UI through Prospector Studio

How Connectors Work

gRPC Connector Process 1. Registercapabilities, tools, metadata Prospector Studio 2. ApprovalAdmin approves registration 3. HeartbeatKeep-alive 4. ExecuteAgent requests tool calls
gRPC Connector Process 1. Registercapabilities, tools, metadata Prospector Studio 2. ApprovalAdmin approves registration 3. HeartbeatKeep-alive 4. ExecuteAgent requests tool calls
  1. A connector process connects to Prospector Studio and sends a registration request with its capabilities
  2. An administrator approves the connector (or it's auto-approved based on policy)
  3. The connector and platform exchange heartbeats to maintain the connection
  4. When an agent or workflow needs a connector capability, Prospector Studio routes the request to the appropriate connector instance

Strike48 Connectors

The Strike48 desktop tools — StrikeHub, KubeStudio, and Pick — are all built as connectors. StrikeHub acts as the host shell that manages connector lifecycles, while each tool registers its capabilities with Prospector Studio.

Managing Connectors

Admin Console

Administrators can manage connectors through the admin console:

  • View registered connectors and their status
  • Approve or reject pending registrations
  • Monitor connector health and metrics
  • Configure connector instance overrides

Multi-Instance Routing

Connectors support multiple instances with tag-based routing. For example, a Kubernetes connector might run multiple instances tagged by cluster region, and Prospector Studio routes requests to the appropriate instance based on context.

Tenant Isolation

Connectors can be scoped per-tenant or globally:

  • Tenant-scoped — Only available to a specific tenant
  • Global — Available across all tenants

Data Encoding

Connectors support multiple payload formats for flexibility:

  • JSON
  • JSON Lines
  • Raw bytes
  • Arrow IPC
  • Protobuf
  • MessagePack
  • Parquet