Skip to content

connect once · work together, live

a shared workspaceyour agent can actually use.

real tools over MCP — a live taskboard, an infinite canvas, knowledge bundles, structured data, and your git repos. it works as you, on the same board you do, and shows its work.

MCP server URL

https://hardlysimple.com/mcp

.hardlysimple/config.json

{  "version": 1,  "repositoryId": "…",  "remote": "git@github.com:you/app.git"}
Three steps

How it works

  1. 1
    Connect your agent once

    One MCP endpoint works with Claude, Codex, ChatGPT, or any MCP-capable assistant. Sign in with OAuth (scoped, no secrets to paste) or a personal access token. Every tool call runs as you — your ownership, team, and admin rules still apply.

    Connect your agent
  2. 2
    Bind your repo

    Run intake_repository with your git remote and drop the returned binding into .hardlysimple/config.json. Now resolve_repo_context hands the agent your team, board, and defaults automatically — and commits, PRs, and branches on cards link straight back to GitHub.

    Repository settings
  3. 3
    Work together, live

    The agent creates tasks, sketches, knowledge, and structured data as you — appearing live on the board while it works. Everything is attributed: you see exactly what a human did versus which companion (and which model) did the rest.

    Open the app
116 MCP tools

What’s possible

Everything the web app does, your agent can do too — through the same authorization layer. Here’s the toolkit.

Taskboards

Kanban boards with subtasks, assignees, comments, and git links. The agent creates, moves, and closes cards; you watch it happen.

Infinite canvas

Sketch ideas on an Excalidraw canvas. Agents append shapes and node/edge diagrams, drop marks, and link sketches to tasks.

Knowledge bundles

Durable, markdown-native knowledge (OKF concepts) so context survives past a single chat — link it to the tasks it explains.

Databanks

A workspace home that gathers bundles, files, images, sketches, and tables into one organized, foldered container.

SimpleTable

Airtable-like structured data: typed fields, validation, and records the agent inserts and queries through typed tools — never raw SQL.

Repositories

Intake a git remote so cards link to real forge URLs. Keep it personal, or connect it to a team so links resolve for everyone.

Companions

Agents identify themselves (provider, model, effort) and their work is grouped into live sessions you can follow on the board.

Search everything

One fuzzy search spans tasks, knowledge, sketches, tables, and more — so an agent finds prior work instead of repeating it.

Showcases

See it in practice

Done means shipped — and provable

When an agent finishes a card it calls link_commit with your bound repository. The card shows a real, clickable GitHub link — for you and everyone on the team. No more “is this actually built?” — it's one lookup.

Add forge links to cards

Done

Derive commit / PR / branch URLs from the bound repository.

#42 forge linksmergeda1b2c3dgithub.com ↗
AIlinked by a companion · Opus 4.8

Bind the repo once, share it with the team

Intake your remote, write a tiny .hardlysimple/config.json, and resolve_repo_context hands every session your team, board, and defaults. Connect the repo to a team and a teammate who binds the same remote inherits it all.

.hardlysimple/config.json

{
  "version": 1,
  "repositoryId": "…",
  "remote": "git@github.com:you/app.git"
}

resolved context

Team
HardlySimple
Board
MCP — MVP
Repo
github.com/you/app
Default column
Manifesting

From a canvas idea to a live board

Sketch on the infinite canvas, turn strokes into tasks, and watch the agent move cards across the board in real time — with its avatar right on the card while it works.

Ideas

Warm gradient hero

Manifesting

Forge links on cards
Repo intake tool

Facts

OAuth + PAT auth

Structured data, without the SQL

Spin up Airtable-like tables with typed fields and validation. The agent inserts and queries records through typed tools, so your data stays clean and there's no raw SQL surface to get wrong.

CompanyStageOwner
Acme CorpQualifiedMiguel
GlobexNewCompanion
InitechWonMiguel
Scoped by default

OAuth grants start read-only. Write and admin access require explicit consent — scopes only ever narrow what your account can already do.

Your permissions still apply

There's no separate access surface. Ownership, team membership, and admin checks run in the same query layer as the web app.

Always attributable

Every action is logged as a human (web) or a companion (which brand, model, and session over MCP), so the trail never lies.

ready when you are

Bring your agent in.

hardlysimple

People and their companions, in one attributed flow. Connect over MCP in a couple of minutes and start on a board you both can see.