MCP Tools Reference

TeamLoop provides a comprehensive set of MCP tools for querying, building, and synthesizing temporal knowledge.

Query Tools

teamloop_query

Query your knowledge across connected integrations (GitHub, Notion, Linear).

Parameters:

Parameter	Type	Required	Description
`query`	string	Yes	The search query
`sources`	string	No	Comma-separated list: `github`, `notion`, `linear`
`mode`	string	No	Query mode: `current` (default) or `as_of`
`as_of`	string	No	Date in YYYY-MM-DD format (required when mode is `as_of`)

Example:

Query: "authentication architecture"
Sources: "github,notion"
Mode: "current"

Returns: Search results with extraction instructions for building your knowledge graph.

teamloop_timeline

Get a temporal timeline showing how knowledge has evolved.

Parameters:

Parameter	Type	Required	Description
`query`	string	No*	Topic to build timeline for
`entity_id`	string	No*	Get lineage for specific entity
`limit`	number	No	Max entries (default: 20)

*Either query or entity_id is required.

Example:

Query: "database architecture"
Limit: 10

Returns: Chronological timeline of decisions, changes, and documents.

teamloop_evolution

Track how knowledge evolved over a time range.

Parameters:

Parameter	Type	Required	Description
`query`	string	Yes	Topic to track
`from_date`	string	Yes	Start date (YYYY-MM-DD)
`to_date`	string	Yes	End date (YYYY-MM-DD)

Example:

Query: "authentication"
From: "2024-01-01"
To: "2024-12-31"

Returns: Evolution of knowledge grouped by month with supersession events.

teamloop_compare

Compare knowledge between two points in time.

Parameters:

Parameter	Type	Required	Description
`query`	string	Yes	Topic to compare
`date_a`	string	Yes	First date (YYYY-MM-DD)
`date_b`	string	Yes	Second date (YYYY-MM-DD)

Example:

Query: "infrastructure decisions"
Date A: "2024-01-01"
Date B: "2024-06-01"

Returns: What was added, removed, superseded, or unchanged.

Knowledge Graph Tools

teamloop_save_knowledge

Save extracted entities and relationships to your knowledge graph.

Parameters:

Parameter	Type	Required	Description
`entities`	array	Yes	Array of entity objects
`relationships`	array	No	Array of relationship objects

Entity Object:

Field	Type	Required	Description
`type`	string	Yes	DECISION, PERSON, PROJECT, COMPONENT, DOCUMENT, CHANGE
`name`	string	Yes	Entity name
`description`	string	No	Detailed description
`event_date`	string	No	When event occurred (YYYY-MM-DD)
`rationale`	string	No	For decisions: why this was chosen
`alternatives`	array	No	For decisions: other options considered
`status`	string	No	Current status
`source_url`	string	No	Link to original source
`source_integration`	string	No	github, notion, or linear
`source_external_id`	string	No	ID in source system

Relationship Object:

Field	Type	Required	Description
`source_name`	string	Yes	Name of source entity
`source_type`	string	Yes	Type of source entity
`target_name`	string	Yes	Name of target entity
`target_type`	string	Yes	Type of target entity
`relationship_type`	string	Yes	DECIDED_BY, AUTHORED_BY, PART_OF, RELATES_TO, SUPERSEDES, DEPENDS_ON, IMPLEMENTS

Example:

{
  "entities": [
    {
      "type": "DECISION",
      "name": "Adopt PostgreSQL for main database",
      "description": "Chose PostgreSQL over MySQL for better JSON support",
      "event_date": "2024-03-15",
      "rationale": "Need JSONB for flexible schema",
      "alternatives": ["MySQL", "MongoDB"],
      "status": "active"
    }
  ],
  "relationships": [
    {
      "source_name": "Adopt PostgreSQL",
      "source_type": "DECISION",
      "target_name": "Alice",
      "target_type": "PERSON",
      "relationship_type": "DECIDED_BY"
    }
  ]
}

Subgraph Tools

teamloop_create_subgraph

Create a curated collection of entities for specific topics.

Parameters:

Parameter	Type	Required	Description
`name`	string	Yes	Subgraph name
`description`	string	No	What this subgraph represents
`entity_ids`	array	No*	Specific entity IDs to include
`query`	string	No*	Semantic query to find entities
`limit`	number	No	Max entities when using query (default: 20, max: 50)

*Use either entity_ids or query, not both.

Example:

Name: "Auth System Decisions"
Query: "authentication and authorization"
Limit: 30

teamloop_get_subgraph

Retrieve a subgraph with all its entities.

Parameters:

Parameter	Type	Required	Description
`subgraph_id`	string	No*	The subgraph UUID
`name`	string	No*	Find by name instead of ID

*Either subgraph_id or name is required.

teamloop_expand_subgraph

Find related entities to expand a subgraph.

Parameters:

Parameter	Type	Required	Description
`subgraph_id`	string	Yes	The subgraph to expand
`depth`	number	No	Relationship hops (1-3, default: 1)
`include_types`	array	No	Filter by entity types
`auto_add`	boolean	No	Automatically add found entities

Example:

Subgraph ID: "abc123..."
Depth: 2
Include Types: ["DECISION", "COMPONENT"]
Auto Add: true

Journal Tools

teamloop_create_journal_entry

Capture thoughts, decisions, or context as journal entries.

Parameters:

Parameter	Type	Required	Description
`title`	string	Yes	Entry title
`content`	string	Yes	Entry content
`mood`	string	No	reflection, planning, decision, note, question
`tags`	array	No	Categorization tags
`link_entity_ids`	array	No	Explicit entity links
`auto_link`	boolean	No	Auto-find related entities (default: true)

Example:

Title: "Thoughts on microservices migration"
Content: "After reviewing the Auth Service and User Service..."
Mood: "planning"
Tags: ["architecture", "q1-planning"]

Synthesis Tools

teamloop_synthesize

Generate documents from a subgraph using templates.

Parameters:

Parameter	Type	Required	Description
`subgraph_id`	string	Yes	Source subgraph
`template_type`	string	Yes	`brief`, `prd`, or `adr`
`additional_context`	string	No	Extra instructions

Template Types:

brief - Executive summary
prd - Product Requirements Document
adr - Architecture Decision Record

Returns: Job ID for polling completion.

teamloop_get_synthesis_job

Check status and get output of a synthesis job.

Parameters:

Parameter	Type	Required	Description
`job_id`	string	Yes	The synthesis job ID

Returns: Job status (pending, processing, completed, failed) and output when complete.

teamloop_cancel_synthesis_job

Cancel a pending or in-progress synthesis job.

Parameters:

Parameter	Type	Required	Description
`job_id`	string	Yes	The synthesis job ID

Best Practices

Workflow Pattern

Query - Use teamloop_query to search integrations
Extract - Use teamloop_save_knowledge to save entities
Organize - Use teamloop_create_subgraph to group related knowledge
Expand - Use teamloop_expand_subgraph to find connections
Synthesize - Use teamloop_synthesize to generate documents

Temporal Queries

Use mode: "as_of" to see what was known at a specific date
Use teamloop_evolution to track changes over time
Use teamloop_compare to diff knowledge between dates
Use teamloop_timeline for entity-specific lineage

Entity Extraction

Always include event_date from source documents
Use source_url for traceability
Create relationships to connect entities
Use appropriate entity types for better queries