Useful context.
Your execution.

Embedded in your application

Start with the Go library

Index content from sources you control, then retrieve relevant context within a token budget. An in-memory store works out of the box.

go get github.com/sirerun/gist

import "github.com/sirerun/gist"

g, err := gist.New()
if err != nil {
    return err
}
defer g.Close()

_, err = g.Index(ctx, content,
    gist.WithSource("my-guide"))
if err != nil {
    return err
}
results, err := g.Search(ctx, "authentication flow",
    gist.WithBudget(4000))

For catalog publication, immutable packages, discovery, and preparation, use the separate github.com/sirerun/gist/catalog packages. The root text-search library and catalog packages serve different integration needs.

Gist public API and MCP discovery

Free public discovery requires no sign-in or API key. Start with the API entry point and OpenAPI reference, or add the public MCP server below. See the agent guide, official CLI and access details.

No sign-in is required for public directory metadata. Add this Streamable HTTP endpoint to a compatible client:

https://gist.sire.run/directory/mcp

Four tools search, inspect, explain authorization and export descriptors: gist_directory_search, gist_directory_get, gist_directory_authorization, gist_directory_export. Use GET /api/directory/authorization?id=... or gist_directory_authorization with an exact connector ID for provider-sourced setup steps, prerequisites and documentation. Guides report documented or needs_research; documented instructions have not been tested with your account. Exports describe setup requirements. Your client must independently admit tools, connect accounts and execute.

REST: GET /api/directory?q=calendar. Embedded Go: github.com/sirerun/gist/catalog/directory. Browse an evolving catalog; each client determines which integrations it supports and can connect to.

Connect your AI client

Use the hosted MCP endpoint

Add this remote MCP server URL in a client that supports Streamable HTTP and OAuth authorization:

https://gist.sire.run/mcp

1. Make sure your GitHub account has access to a Gist workspace. Sign in to Gist to check your enrollment.
2. Add the URL using your client's remote MCP configuration.
3. Complete the client's OAuth flow and review the requested access. Website sign-in and authorization of an MCP client are separate steps.
4. Ask the client to discover relevant artifacts, retrieve the chosen version, and check its requirements.

The stable discovery interface includes gist_discover, gist_get, and gist_resolve. Available tools and authorization flows vary by client.

Before the work begins

Resolve requirements explicitly

A skill describes a reusable workflow and the capabilities it needs. Gist matches those requirements to authorized, versioned bindings. Your client supplies the available connections and checks whether the workflow is ready.

Missing capabilities or unavailable connections stay visible as unresolved requirements. Finding an artifact does not install a tool, connect an account, or authorize execution.

Keep control in your client

Your client validates inputs, connects provider accounts, asks for user approval, runs tools, and manages retries or recovery. Gist provides catalog content and resolution; it does not execute your workflows.