every ai agent in your organisation shares one source of truth — a git repo. no database. no hosted service. just your team’s context in markdown.
fork the repo, fill in your team’s context, and connect any mcp-compatible ai tool.
copy organisation.md into your github org. the template includes identity, team, projects, decisions, and preferences sections.
edit the markdown files with your org’s actual data — who does what, which projects are active, past decisions.
start with npx @shashank-sn/organisation-md. your ai agents connect over stdio and read/write context naturally.
every context change goes through a pull request. no silent writes into agent state.
an agent proposes a context update — becomes a pr.
teammates discuss, approve, or request changes.
approved changes become permanent context.
every agent that starts sees the updated context.
read, search, and propose updates to your organisation’s context — all through pull requests.
read_org
read the full organisation.md file from the github repo.
read_section
read a specific section by heading (e.g. team, decisions).
update_section
propose an update to any section — creates a pull request.
search_context
search across organisation.md and all context files.
propose_change
propose a change to any tracked file — creates a pr.
list_context_files
list all files in the context directory.
import_file
import a txt, md, or docx file into the knowledge base.
add_info
add info via natural language — auto-detects the section.
remove_info
remove info via natural language — auto-detects what to remove.
check_roles
check which users can modify which files.
check_permissions
check a user’s permissions across the repo.
configure_codeowners
set up codeowners for path-level access control.
report_bug
auto-detect the area and file a github issue.
suggest_feature
suggest a feature — creates a github issue automatically.
one environment variable. one npx command. no database setup, no deployment pipeline.
upload folders of .txt, .md, or .docx files. the server parses them, creates context entries, and updates organisation.md as your navigation index.
point the server at a folder of files. every .txt, .md, and .docx file becomes a context entry under context/.
add, edit, or remove information by speaking naturally. the server parses your intent and updates the right files.
control who can add, delete, or approve changes through git itself — codeowners, branch protection, and commit signing.
the repo structure is designed to grow with your team. start with the template, add context files as you go.
canonical context file — identity, mission, team, projects, decisions, and more.
supporting docs for projects, architecture, people, and anything else that deserves its own file.
typescript mcp server with octokit integration, markdown parser, and tool implementations.
quickstart guide, agent prompt template, example flows, and product strategy.