Folk MCP by usefulapi

Reviewed 1d ago.

• tools: 14 tools scanned
• metadata: scanned

No findings.

Tools (14)

• folk_get_current_user

  Get the user associated with the current Folk API key. Folk REST: GET /v1/users/me.

• folk_list_users

  List users in the Folk workspace (id, name, email) — useful for resolving owner ids. Folk REST: GET /v1/users.

• folk_list_people

  List/filter people (contacts). Supports cursor pagination and structured filters. Folk REST: GET /v1/people.

• folk_get_person

  Get a single person (contact) by id. Folk REST: GET /v1/people/{id}.

• folk_list_companies

  List/filter companies. Supports cursor pagination and structured filters. Folk REST: GET /v1/companies.

• folk_get_company

  Get a single company by id. Folk REST: GET /v1/companies/{id}.

• folk_list_groups

  List groups in the Folk workspace (ids needed to place people/companies). Folk REST: GET /v1/groups.

• folk_list_notes

  List notes, optionally scoped to an entity or filtered by full text and creation date. Folk REST: GET /v1/notes.

• folk_get_note

  Get a single note by id. Folk REST: GET /v1/notes/{id}.

• folk_create_person

  Create a new person (contact). All fields are optional. Folk REST: POST /v1/people.

• folk_update_person

  Update fields on an existing person. Only provided fields are changed; list-valued fields (emails, phones, groups, companies, etc.) REPLACE the existing values. Folk REST: PATCH /v1/people/{id}.

• folk_create_company

  Create a new company. `name` is required. Folk REST: POST /v1/companies.

• folk_update_company

  Update fields on an existing company. Only provided fields are changed; list-valued fields REPLACE the existing values. Folk REST: PATCH /v1/companies/{id}.

• folk_create_note

  Create a note attached to an entity (person/company). Folk REST: POST /v1/notes.