Sourcegraph Automation

What This Skill Does

• The Sourcegraph Automation skill automates operations within Sourcegraph through Composio's Sourcegraph toolkit via Rube MCP.
• It is designed for users who need to manage and interact with their Sourcegraph instances programmatically.
• This skill streamlines workflows by enabling automated tool discovery, connection management, and tool execution.

When to Use

• Automate code searches in Sourcegraph.
• Manage Sourcegraph repositories programmatically.
• Search for code patterns within Sourcegraph.
• Trigger code intelligence features in Sourcegraph.
• Sync code data between systems and Sourcegraph.
• Create automated code analysis workflows.

Key Features

• Automates Sourcegraph operations via Rube MCP.
• Uses RUBE_SEARCH_TOOLS for dynamic tool discovery.
• Manages Sourcegraph connections via RUBE_MANAGE_CONNECTIONS.
• Executes tools with schema-compliant arguments.
• Provides a structured workflow pattern for automation.
• Offers guidance on avoiding common pitfalls.

Manual Installation

Sourcegraph Automation via Rube MCP

Automate Sourcegraph operations through Composio's Sourcegraph toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/sourcegraph

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Sourcegraph connection via RUBE_MANAGE_CONNECTIONS with toolkit sourcegraph Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

• Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration.
• No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit sourcegraph If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS queries: [{use_case: "Sourcegraph operations", known_fields: ""}] session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Sourcegraph task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["sourcegraph"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"

Known Pitfalls

• Always search first: Tool schemas change.
• Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS. Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Schema compliance: Use exact field names and types from the search results Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
• Session reuse: Reuse session IDs within a workflow.
• Generate new ones for new workflows. Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference