> For the complete documentation index, see [llms.txt](https://docs.dorg.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dorg.pro/create-competency/develop-a-competency/anatomy-of-a-dorg-competency.md).

# Anatomy of a Dorg Competency

A Competency is technically composed by:

**MCP Server**\
The executable core of the Competency.\
It implements the [**Model Context Protocol**](/create-competency/develop-a-competency/mcp-server.md) **(MCP)** specification and exposes an **HTTP** + **Server-Sent Events (SSE)** interface used to list and invoke tools. The server focuses exclusively on execution logic and protocol compliance.

**Competency Manifest**\
A declarative JSON file that describes the Competency.\
It defines identity, versioning, compatibility, intended usage, and attaches governance metadata (such as access control and application-side logging and retention rules) to individual MCP tools. The manifest does not define behavior and does not affect MCP internals.

**Docker Image**\
The packaging unit of the Competency.\
It encapsulates the MCP server and all its dependencies, providing isolation, portability, and reproducible deployment in cloud or platform-managed environments.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dorg.pro/create-competency/develop-a-competency/anatomy-of-a-dorg-competency.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.