Pylon MCP Server

Instructions

Implementation Reference

• src/index.ts:288-305 (registration)

  MCP tool registration for 'pylon_list_issues', including the description, Zod input schema for start_time and end_time, and the inline handler function that invokes PylonClient.listIssues and formats the response as JSON text.

  server.tool(
  	'pylon_list_issues',
  	'List issues within a time range (max 30 days)',
  	{
  		start_time: z
  			.string()
  			.describe('Start time in RFC3339 format (e.g., 2024-01-01T00:00:00Z)'),
  		end_time: z
  			.string()
  			.describe('End time in RFC3339 format (e.g., 2024-01-31T00:00:00Z)'),
  	},
  	async ({ start_time, end_time }) => {
  		const result = await client.listIssues(start_time, end_time);
  		return {
  			content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
  		};
  	},
  );

• src/pylon-client.ts:273-284 (handler)

  Core handler logic in PylonClient.listIssues method: constructs query parameters for start_time and end_time, makes a GET request to the Pylon API /issues endpoint, and returns paginated list of issues.

  async listIssues(
  	startTime: string,
  	endTime: string,
  ): Promise<PaginatedResponse<Issue>> {
  	const searchParams = new URLSearchParams();
  	searchParams.set('start_time', startTime);
  	searchParams.set('end_time', endTime);
  	return this.request<PaginatedResponse<Issue>>(
  		'GET',
  		`/issues?${searchParams.toString()}`,
  	);
  }

• src/pylon-client.ts:55-72 (schema)

  TypeScript interface defining the structure of an Issue object returned by the listIssues API call.

  export interface Issue {
  	id: string;
  	title: string;
  	state: string;
  	priority?: string;
  	body_html?: string;
  	assignee_id?: string;
  	team_id?: string;
  	account_id?: string;
  	contact_id?: string;
  	requester_id?: string;
  	tags?: string[];
  	created_at?: string;
  	updated_at?: string;
  	customer_portal_visible?: boolean;
  	issue_type?: string;
  }