Skip to content
slashh

For developers

Give your agents company context.

An MCP interface and a framework adapter for cited, permission-aware memory. Keep orchestration in your application; bring the relevant context into each request.

  1. Prepare your environment

    Use a running Slashh server and a built local MCP checkout. During private preview, we can help provision the environment.

  2. Create a scoped principal

    Issue an agent key through your authenticated administration flow. Limit its scopes to the workflow and keep it out of source control.

  3. Connect your MCP client

    Set the local build path, server URL and issued key in your client’s MCP configuration. The values shown here are placeholders.

MCP configuration / local setup
{
  "mcpServers": {
    "slashh": {
      "command": "node",
      "args": ["/absolute/path/to/mcp/dist/index.js"],
      "env": {
        "SLASHH_API_BASE": "http://localhost:4001",
        "SLASHH_AGENT_KEY": "REPLACE_WITH_AGENT_KEY"
      }
    }
  }
}

The interface

Tools that speak your company’s language.

A selection of the MCP tools. Available results depend on the principal’s permissions and granted scopes.

memory_search

Retrieve ranked context with source citations.

memory_ask

Ask a question and get a grounded answer.

entity_profile

Explore the relationships around a person or project.

who_knows

Find people connected to a topic.

decisions

Retrieve decision records and their context.

glossary_define

Look up your company’s terminology.

timemachine_diff

Compare facts about an entity across dates.

memory_write

Record agent-authored facts with provenance.

Use your own orchestration

A small adapter. The same memory.

The framework adapter exposes search, recall and writes through the Slashh REST client. This example assumes the workspace package is built and available to your application.

TypeScript / framework adapter
import { SlashhMemory } from "@slashh/mcp/framework-adapter";

const memory = new SlashhMemory({
  baseUrl: process.env.SLASHH_API_BASE ?? "http://localhost:4001",
  apiKey: process.env.SLASHH_AGENT_KEY,
});

const answer = await memory.recall(
  "Why did we move the launch?"
);

console.log(answer.text, answer.citations);

Before the first call

Make the boundaries explicit.

Credentials stay server-side

Do not embed an agent key in browser code. Store it in the execution environment and rotate it through your administration process.

Permissions follow the request

Test with a narrowly scoped principal. Verify both permitted retrieval and refusal behavior before adding the tool to an autonomous workflow.

Inspect the evidence

Handle missing context and ungrounded results in your application. Citations are part of the response, not optional decoration.

Time is part of the context

Read tools that support as_of accept a historical timestamp. Evaluate which time boundary your workflow needs.

Your next step

Build against your own questions.

Discuss a development environment, source connections and the workflow you want your agent to handle.

Discuss an integration