For people working with coding agents

Turn research into an agent’s next clear move.

Tessli helps a person frame a design task, choose useful sources, keep the decisions that matter, and hand over compact context for implementation and review. It routes research; it does not promise a finished outcome.

Start with a task Open local Boards

One shared workflow

From task to reviewed implementation.

The useful unit is not a giant catalogue dump. It is a task, a small source set, and the project decisions that travel with it.

State the task
Name the surface, constraints, and the question the build needs to answer.
Retrieve for task fit
Start with a small source set and the recorded reason each source belongs.
Inspect the source guide
Use the guide to see what to explore, the access route, limitations, and alternatives.
Keep the decision
Save useful sources or add them to a local Board with selected, rejected, and open decisions.
Hand off compact context
Copy or download the Board’s Markdown or JSON, then explicitly give it to the agent.
Build and review
The agent implements; browser review and a human decision determine what the project keeps.

What an agent receives

Guidance with a reason to use it.

Each source guide makes the practical next step visible: what a source helps with, what to inspect, how to access it, one important limitation, and differentiated alternatives.

Task-fit guidance

Retrieval is deterministic and grounded in the recorded source profile. It returns a bounded shortlist instead of treating every source as equally relevant.

Access that names the route

A source can point to a browser, documentation, registry, source code, API, MCP, CLI, or plugin—only where that route is recorded.

Project-owned decisions

A local Board preserves why a source was selected or rejected, plus constraints and questions the agent should not guess.

A concrete task, kept compact

A result a builder can act on.

This example uses recorded canonical data—not a simulated provider preview or a generic recommendation.

Task

Add a code-owned, accessible settings panel to a Next.js/Tailwind product.

Needs: Accessible components, implementation guidance
Keep in view: Custom visual language, not a copied template

One recorded result

shadcn/ui

Copyable React components built with Radix UI and Tailwind CSS

Fits the recorded React, Tailwind, and Next.js framework context.
Supports recorded accessible-component and design-system setup workflows.
Limitation: Components are unstyled primitives requiring Tailwind styling

Inspect the shadcn/ui source guide

Access without MCP

Use a source guide or public representation.

An agent does not need a Tessli-specific integration to receive canonical source guidance. Send a stable source-guide URL, or use its public JSON or Markdown representation.

Semantic source pages

The public source guide is designed for direct reading and links to the recorded provider route separately.

Open the source guide

Public JSON and Markdown

These static representations expose the same source truth in a compact, model-neutral form.

Source JSON Source Markdown

Current transport

Local MCP is the current transport.

Tessli MCP is a read-only process that an MCP client starts from a checked-out repository. It can retrieve task-fit source guidance and compact research briefs from the same canonical data.

Run it from the repository

Install the locked dependencies, then start the local server from the web workspace. It waits for an MCP client over standard input and output.

git clone https://github.com/itsdeepaks/tessli.git
cd tessli/web
npm ci
npm run mcp

Let the client start the process

Configure your MCP client with the repository location. Field names vary by client; replace the example path on your machine.

{
  "mcpServers": {
    "tessli": {
      "command": "npm",
      "args": ["run", "mcp"],
      "cwd": "/absolute/path/to/tessli/web"
    }
  }
}

Open the Tessli repository

Remote and hosted MCP are unavailable today. Do not configure an endpoint, and do not expect Tessli to access provider accounts, browser state, or local Board data.

Access-route vocabulary

Choose the recorded access route.

Tessli names an allowed next step; it does not proxy a provider, supply credentials, or stand in for a provider’s terms.

Read: Browser or documentation for inspection and guidance.
Integrate: Package registry, source code, API, CLI, or plugin where recorded.
Connect: MCP only when a source records a provider-owned endpoint and its access boundary.

A concise boundary

Keep project context private and provider boundaries clear.

Tessli routes agents to recorded public source paths. It does not mirror paid or private provider content, bypass access controls, supply provider credentials, ingest a project automatically, or make a hidden write on a person’s behalf.