Skip to content

Add Collibra Data Access MCP tools - #117

Draft
wouterc-collibra wants to merge 21 commits into
mainfrom
data-access-tools
Draft

Add Collibra Data Access MCP tools#117
wouterc-collibra wants to merge 21 commits into
mainfrom
data-access-tools

Conversation

@wouterc-collibra

Copy link
Copy Markdown

🎯 What does this PR do?

Adds MCP tools for Collibra Data Access:

  • search_data_access_identities - search Data Access users by name/email
  • search_data_access_objects - search data objects (tables, columns, schemas, views, etc.)
  • get_data_access_data_source - resolve a data source ID to name/type/description
  • get_data_access_control_details - retrieve details of a single access control
  • check_user_data_object_access - check whether a user has access to one or more data objects
  • create_data_access_request - create a new Data Access request

Also includes the collibra/data-access skill guiding agents through WHO/WHAT resolution before checking access or creating requests.

✅ Checklist

  • My code follows the style guidelines of this project.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have made corresponding changes to the documentation (if needed).
  • My commit messages follow the Conventional Commits standard.

wouterc-collibra and others added 18 commits May 8, 2026 16:33
# Conflicts:
#	go.mod
#	go.sum
#	pkg/tools/tools_register.go
# Conflicts:
#	SKILLS.md
#	pkg/tools/register.go
# Conflicts:
#	README.md
#	pkg/tools/register.go
# Conflicts:
#	README.md
#	go.mod
#	go.sum
#	pkg/tools/register.go
… skill doc

get_data_access_control_details was fully implemented but never wired into
RegisterAll after a branch merge dropped it. Also fixes README links that
pointed to the wrong tool directories and removes a stale nextCursor
pagination claim in the data-access SKILL.md that doesn't match the
search_data_access_identities implementation.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@svc-snyk-github-jira

svc-snyk-github-jira commented Aug 5, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

wouterc-collibra and others added 3 commits August 5, 2026 22:54
go.mod requires go 1.26.5 (data-access-go-sdk needs >=1.26.4), but CI
was pinned to 1.25.0 with GOTOOLCHAIN=local, failing the build step.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Six data-access tools were missing Title and required
mcp.ToolAnnotations fields (OpenWorldHint, IdempotentHint for
read-only tools), failing TestRegisterAll_AllToolsHaveProperAnnotations.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
golangci-lint v2.4.0 was built with go1.25 and refuses to lint a
module targeting go1.26.5. Bumping to v2.12.2 (built with a newer
toolchain) unblocks the Lint step.

Also fixes the staticcheck QF1008 findings it then surfaced: several
genqlient-generated SDK types embed a field with the same name as the
struct (e.g. AccessControl.AccessControl.Id), so the outer field name
can be dropped from the selector.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants