development-tools

Development Tools

Auto-generated from 5 exported tool(s) in the Context Engine.

create_feature_pr

Update a Feature entity with Pull Request information. Call this after creating a PR via gh CLI.

Call mcp__tabnine-ctx-cloud__create_feature_pr with parameters:

Parameter	Type	Required	Description
featureName	string	Yes	The feature name to update
prNumber	number	Yes	The PR number
prUrl	string	Yes	The full PR URL
prTitle	string	Yes	The PR title
reviewers	string	No	Comma-separated list of reviewer usernames
filesChanged	string	No	Comma-separated list of changed files

get_feature

Retrieve information about a Feature entity by name.

Call mcp__tabnine-ctx-cloud__get_feature with parameters:

Parameter	Type	Required	Description
featureName	string	Yes	The feature name to look up

merge_feature_pr

Mark a Feature as merged. Call this after successfully merging the PR.

Call mcp__tabnine-ctx-cloud__merge_feature_pr with parameters:

Parameter	Type	Required	Description
featureName	string	Yes	The feature name to mark as merged
mergeCommit	string	No	The merge commit SHA

start_new_feature

Register a new development feature in the Context Engine. Creates a Feature entity to track the feature lifecycle including branch, worktree, decisions, and PR info. Call this after creating the git worktree and feature branch.

Call mcp__tabnine-ctx-cloud__start_new_feature with parameters:

Parameter	Type	Required	Description
featureName	string	Yes	The feature name (used as entity name)
branchName	string	Yes	The full git branch name (e.g., feature/my-feature)
worktreePath	string	Yes	Relative path to the worktree (e.g., .worktrees/my-feature)
baseBranch	string	No	The base branch (default main)
description	string	No	Brief description of the feature

update_feature_decisions

Add a design decision to an existing Feature entity. Use this to record architectural choices, implementation decisions, and their rationale.

Call mcp__tabnine-ctx-cloud__update_feature_decisions with parameters:

Parameter	Type	Required	Description
featureName	string	Yes	The feature name to update
decision	string	Yes	The design decision that was made
rationale	string	Yes	The reasoning behind this decision
alternatives	string	No	Alternative approaches considered