Bug Reports bug_reports
File a bug report about Kenso for the Kenso team, with optional files. Only after the user explicitly says yes to the drafted report. notes-create adds the user's later words to a report filed in the last 24 hours, instead of filing it again.
Call it from an MCP client connected to https://mcp.ken.so/mcp: changes through bug_reports_write. Each takes operation plus that operation's parameters, and your workspace role decides which operations you see.
Each operation with a route calls the Kenso API at https://api.ken.so with Authorization: Bearer <Kenso API key>, Ken-Version: 1.1 and X-Ken-Workspace-Id: <workspace id>. You can call that route directly with the same headers.
Operations: create, notes-create
create
Write. Early access: needs bug_reports on for the workspace. POST https://api.ken.so/v1/bug-reports
File a bug report about Kenso for the Kenso team, only after the user says yes. Put the user's own words in description and show them the report first. Returns status received and an opaque id.
POST /api/v1/bug-reports. Sends Ken-Version 1.1. Multipart. Behind the bug_reports feature:
a workspace without it does not list the operation.
NEVER file a report without the user's explicit yes. Draft it, show it, wait for the yes, and
file once per problem. The reporter gets no reference number or link back: tell them the report
was received and the Kenso team will look at it. The result's data.id is not a reference number
to show: keep it, and when the user adds something about the same problem within 24 hours, add
it with bug_reports(operation="notes-create", bug_report_id=..., note=...) instead of filing again.
description is required: the user's own words about what went wrong (at most 10,000 characters).
title is a short headline (at most 120). summary is yours to write: the steps to reproduce, then
expected versus actual (at most 10,000). page_url is the Kenso page the user was on (at most 2,000).
diagnostics is a JSON object (or its JSON text, or plain text; at most 20,000 characters as sent):
the failing tool, operation, error text and any request id. transcript is the relevant part of the conversation (at most 60,000).
support_attachment_ids are ids of files already uploaded in Kenso's support chat (at most 5).
files is a list of {"file_name": str, "file_content_base64": str}, at most 10 files of at most
26,214,400 bytes each and 50,000,000 bytes together once decoded. Executables and scripts are refused: .exe, .dll, .js, .sh,
.ps1, .py, .html, .svg, disk images (.iso, .img), macro Office files (.docm, .xlsm) and similar.
The hosted MCP cannot read the caller's machine, so there is no file_path:
read the file and pass its bytes in base64.
source is honored only for Kenso's own agents (support_chat or ken_agent); any other client is
recorded as mcp with its client name.
notes-create
Write. Early access: needs bug_reports on for the workspace. POST https://api.ken.so/v1/bug-reports/{bugReportId}/notes
Path: bugReportId
Body (json): note string
Add the user's note to a bug report they filed, only after the user says yes. bug_report_id is data.id from the create result. Returns status received.
POST /api/v1/bug-reports/{bugReportId}/notes. Sends Ken-Version 1.1. JSON body. Behind the
bug_reports feature, like create.
Use it when the user adds something about a problem already reported in this conversation,
instead of filing the same problem twice. Show the note and wait for the user's yes first.
bug_report_id is the id bug_reports(operation="create", ...) returned. note is required: the
user's own words, at most 10,000 characters once trimmed.
Only the person who filed the report can add a note, in the same workspace, within 24 hours
of filing; any other id answers not_found. Each note counts toward the same daily limits as a
report (20 per person, 50 per workspace).